Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Content Management Service
  4. Data Integration Service
  5. Data Integration Service Architecture
  6. Data Integration Service Management
  7. Data Integration Service Grid
  8. Data Integration Service Applications
  9. Mass Ingestion Service
  10. Metadata Access Service
  11. Metadata Manager Service
  12. Model Repository Service
  13. PowerCenter Integration Service
  14. PowerCenter Integration Service Architecture
  15. High Availability for the PowerCenter Integration Service
  16. PowerCenter Repository Service
  17. PowerCenter Repository Management
  18. PowerExchange Listener Service
  19. PowerExchange Logger Service
  20. SAP BW Service
  21. Search Service
  22. System Services
  23. Test Data Manager Service
  24. Test Data Warehouse Service
  25. Web Services Hub
  26. Application Service Upgrade
  27. Application Service Databases
  28. Connecting to Databases from Windows
  29. Connecting to Databases from UNIX
  30. Updating the DynamicSections Parameter of a DB2 Database

Environment Variables for MapR

Environment Variables for MapR

If you use the Analyst tool to run profiles against Hive data objects, configure properties on the Analyst Service to enable communication between the Analyst tool and the cluster, including testing of the Hive connection.
The following table describes the MapR properties:
Property
Value
JAVA_OPTS
-Dhadoop.login=<MAPR_ECOSYSTEM_LOGIN_OPTS> -Dhttps.protocols=TLSv1.2
where <MAPR_ECOSYSTEM_LOGIN_OPTS> is the value of the MAPR_ECOSYSTEM_LOGIN_OPTS property in the file
/opt/mapr/conf/env.sh
.
MAPR_HOME
MapR client directory on the machine that runs the Data Integration Service.
For example,
opt/mapr
Required if you want to fetch a MapR Streams data object.
MAPR_TICKETFILE_LOCATION
Required when the MapR cluster is ticketed. Directory where an additional MapR Ticket file is stored on the machine that runs the Data Integration Service.
When the MapR cluster is configured to enable a user to use Kerberos authentication and MapR Ticket authentication, generate a MapR ticket file for the user for each authentication mode. Save one ticket file in
/tmp
. Save the other ticket file in any directory on the Data Integration Service machine, and provide the location as the value for this property.
For example, for a user id 1234, save a MapR ticket file named like
maprticket_1234
in
/tmp
, and save another MapR ticket file named like
maprticket_1234
in the MAPR_TICKETFILE_LOCATION.
The ticket files can have the same or different names. You must generate the MapR ticket files separately and save one to the MAPR_TICKETFILE_LOCATION.
Changes take effect when you restart the Analyst Service.