Apache Hive Sources > Before you begin > Create a connection
  

Create a connection

Create a Hive Connector connection object in Administrator.
Before you create a connection, configure the Hive Connector to download the Hive third-party libraries for Cloudera CDP, Amazon EMR, or the Azure HDInsight cluster. You can also connect to Apache Hive source systems hosted on the Google Cloud Dataproc cluster using non-Kerberos authentication. For more information about the Hive Connector, see Hive Connector in the Data Integration Connectors help.
    1In Administrator, select Connections.
    2Click Add Connection.
    3Select the Hive Connector connection type.
    4In the Connection Details section, enter the following connection details:
    Connection property
    Description
    Connection Name
    Name of the connection.
    Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
    Maximum length is 255 characters.
    Description
    Description of the connection. Maximum length is 4000 characters.
    5In the Hive Connector Properties section, select the runtime environment where you want to run the tasks.
    6In the Connection section, enter the following connection details:
    Connection property
    Description
    Use Secret Vault
    Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
    This property appears only if secrets manager is set up for your organization.
    When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
    Note:
    If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
    For information about how to configure and use a secrets manager, see Secrets manager configuration.
    Authentication Type
    You can select one of the following authentication types:
    • - Kerberos. Select Kerberos for a Kerberos cluster.
    • - LDAP. Select LDAP for an LDAP-enabled cluster.
      • Note:
      LDAP is not applicable to mappings in advanced mode.
    • - None. Select None for a Hadoop cluster that is not secure or not LDAP-enabled.
    JDBC URL *
    The JDBC URL to connect to Hive.
    Specify the following format based on your requirement:
    • - To view and import tables from a single database, use the following format: jdbc:hive2://<host>:<port>/<database name>
    • - To view and import tables from multiple databases, do not enter the database name. Use the following JDBC URL format: jdbc:hive2://<host>:<port>/
      • Note:
      After the port number, enter a slash.
    • - To access Hive on a Hadoop cluster enabled for TLS, specify the details in the JDBC URL in the following format: jdbc:hive2://<host>:<port>/<database name>;ssl=true;sslTrustStore=<TrustStore_path>;trustStorePassword=<TrustStore_password>,
      • where the truststore path is the directory path of the truststore file that contains the TLS certificate on the agent machine.
    JDBC Driver *
    The JDBC driver class to connect to Hive.
    Username
    The user name to connect to Hive in LDAP or None mode.
    Password
    The password to connect to Hive in LDAP or None mode.
    Principal Name
    The principal name to connect to Hive through Kerberos authentication.
    Keytab Location
    The path and file name to the Keytab file for Kerberos login.
    Configuration Files Path *
    The directory that contains the Hadoop configuration files for the client.
    Copy the site.xml files from the Hadoop cluster and add them to a folder in the Linux box. Specify the path in this field before you use the connection in a mapping to access Hive on a Hadoop cluster:
    • - For mappings, you require the core-site.xml, hdfs-site.xml, and hive-site.xml files.
    • - For mappings in advanced mode, you require the core-site.xml, hdfs-site.xml, hive-site.xml, mapred-site.xml, and yarn-site.xml files.
    * These fields are mandatory parameters.
    7Click Test to test your connection to the source system.
    8Click Save.