Table of Contents


  1. Preface
  2. Introduction to Hadoop Integration
  3. Before You Begin
  4. Amazon EMR Integration Tasks
  5. Azure HDInsight Integration Tasks
  6. Cloudera CDH Integration Tasks
  7. Hortonworks HDP Integration Tasks
  8. MapR Integration Tasks
  9. Appendix A: Connections

Generate Tickets

Generate Tickets

After you create a MapR user account for the Data Integration Service user, name the ticket file using the following naming convention:
maprticket_<user name>
For example, for a user ID 1234, a MapR ticket file named maprticket_1234 is generated.
Save the ticket on the machines that host the Data Integration Service, the Metadata Access Service, and the Analyst Service. The Data Integration Service and the Analyst Service access the ticket at run time. The Metadata Access Service access the ticket for the Developer tool at design time.
By default, the services access the ticket in the /tmp directory. If you save the ticket to any other location, you must configure the MAPR_TICKETFILE_LOCATION environment variable in the service properties.


We’d like to hear from you!