User Guide

10.1
- 10.5
- 10.4.1
- 10.4.0
- 10.2.2 HotFix 1
- 10.2.2 Service Pack 1
- 10.2.2
- 10.2.1
- 10.2 HotFix 1
- 10.2
- 10.1.1 Update 2
- 10.1.1 HotFix 1
- 10.1.1
- 10.0

Back Next

Hive Connection Properties

Use the Hive connection to access Hive data. A Hive connection is a database type connection. You can create and manage a Hive connection in the Administrator tool, Analyst tool, or the Developer tool. Hive connection properties are case sensitive unless otherwise noted.

The order of the connection properties might vary depending on the tool where you view them.

The following table describes Hive connection properties:

Property	Description
Name	The name of the connection. The name is not case sensitive and must be unique within the domain. You can change this property after you create the connection. The name cannot exceed 128 characters, contain spaces, or contain the following special characters: ~ ` ! $ % ^ & * ( ) - + = { [ } ] \| \ : ; " ' < , > . ? /
ID	String that the Data Integration Service uses to identify the connection. The ID is not case sensitive. It must be 255 characters or less and must be unique in the domain. You cannot change this property after you create the connection. Default value is the connection name.
Description	The description of the connection. The description cannot exceed 4000 characters.
Location	The domain where you want to create the connection. Not valid for the Analyst tool.
Type	The connection type. Select Hive.
Connection Modes	Hive connection mode. Select at least one of the following options: Access HiveServer2 to run mappings. Select this option if you want to use Hive as a source or a target. You can enable the same connection or another Hive connection to run mappings in HiveServer2 in the Hadoop cluster. Access Hive CLI to run mappings. Select this option if you want to use the Hive CLI to run mappings in the Hadoop cluster. You can select both the options. If you select both the options, the connection created can be used for Hive as a source or target or to run the mapping in the Pushdown mode.
User Name	User name of the user that the Data Integration Service impersonates to run mappings on a Hadoop cluster. The user name depends on the JDBC connection string that you specify in the Metadata Connection String or Data Access Connection String for the native environment. If the Hadoop cluster runs Hortonworks HDP, you must provide a user name. If you use Tez to run mappings, you must provide the user account for the Data Integration Service. If you do not use Tez to run mappings, you can use an impersonation user account. If the Hadoop cluster uses Kerberos authentication, the principal name for the JDBC connection string and the user name must be the same. Otherwise, the user name depends on the behavior of the JDBC driver. With Hive JDBC driver, you can specify a user name in many ways and the user name can become a part of the JDBC URL. If the Hadoop cluster does not use Kerberos authentication, the user name depends on the behavior of the JDBC driver. If you do not specify a user name, the Hadoop cluster authenticates jobs based on the following criteria: The Hadoop cluster does not use Kerberos authentication. It authenticates jobs based on the operating system profile user name of the machine that runs the Data Integration Service. The Hadoop cluster uses Kerberos authentication. It authenticates jobs based on the SPN of the Data Integration Service.
Common Attributes to Both the Modes: Environment SQL	SQL commands to set the Hadoop environment. In native environment type, the Data Integration Service executes the environment SQL each time it creates a connection to a Hive metastore. If you use the Hive connection to run profiles in the Hadoop cluster, the Data Integration Service executes the environment SQL at the beginning of each Hive session. The following rules and guidelines apply to the usage of environment SQL in both connection modes: Use the environment SQL to specify Hive queries. Use the environment SQL to set the classpath for Hive user-defined functions and then use environment SQL or PreSQL to specify the Hive user-defined functions. You cannot use PreSQL in the data object properties to specify the classpath. The path must be the fully qualified path to the JAR files used for user-defined functions. Set the parameter hive.aux.jars.path with all the entries in infapdo.aux.jars.path and the path to the JAR files for user-defined functions. You can use environment SQL to define Hadoop or Hive parameters that you want to use in the PreSQL commands or in custom queries. If you use multiple values for the Environment SQL property, ensure that there is no space between the values. The following sample text shows two values that can be used for the Environment SQL: set hive.execution.engine='tez';set hive.exec.dynamic.partition.mode='nonstrict'; If you use the Hive connection to run profiles in the Hadoop cluster, the Data Integration service executes only the environment SQL of the Hive connection. If the Hive sources and targets are on different clusters, the Data Integration Service does not execute the different environment SQL commands for the connections of the Hive source or target.

Properties to Access Hive as Source or Target

The following table describes the connection properties that you configure to access Hive as a source or target:

Property	Description
Metadata Connection String	The JDBC connection URI used to access the metadata from the Hadoop server. You can use PowerExchange for Hive to communicate with a HiveServer service or HiveServer2 service. To connect to HiveServer, specify the connection string in the following format: jdbc:hive2://<hostname>:<port>/<db> Where <hostname> is name or IP address of the machine on which HiveServer2 runs. <port> is the port number on which HiveServer2 listens. <db> is the database name to which you want to connect. If you do not provide the database name, the Data Integration Service uses the default database details. To connect to HiveServer 2, use the connection string format that Apache Hive implements for that specific Hadoop Distribution. For more information about Apache Hive connection string formats, see the Apache Hive documentation.
Bypass Hive JDBC Server	JDBC driver mode. Select the check box to use the embedded JDBC driver mode. To use the JDBC embedded mode, perform the following tasks: Verify that Hive client and Informatica services are installed on the same machine. Configure the Hive connection properties to run mappings in the Hadoop cluster. If you choose the non-embedded mode, you must configure the Data Access Connection String. Informatica recommends that you use the JDBC embedded mode.
Data Access Connection String	The connection string to access data from the Hadoop data store. To connect to HiveServer, specify the non-embedded JDBC mode connection string in the following format: jdbc:hive2://<hostname>:<port>/<db> Where <hostname> is name or IP address of the machine on which HiveServer2 runs. <port> is the port number on which HiveServer2 listens. <db> is the database to which you want to connect. If you do not provide the database name, the Data Integration Service uses the default database details. To connect to HiveServer 2, use the connection string format that Apache Hive implements for the specific Hadoop Distribution. For more information about Apache Hive connection string formats, see the Apache Hive documentation.

Properties to Run Mappings in Hadoop Cluster

The following table describes the Hive connection properties that you configure when you want to use the Hive connection to run Informatica mappings in the Hadoop cluster:

Property	Description
Database Name	Namespace for tables. Use the name default for tables that do not have a specified database name.
Default FS URI	The URI to access the default Hadoop Distributed File System. Use the following connection URI: hdfs://<node name>:<port> Where <node name> is the host name or IP address of the NameNode. <port> is the port on which the NameNode listens for remote procedure calls (RPC). If the Hadoop cluster runs MapR, use the following URI to access the MapR File system: maprfs:/// .
JobTracker/Yarn Resource Manager URI	The service within Hadoop that submits the MapReduce tasks to specific nodes in the cluster. Use the following format: <hostname>:<port> Where <hostname> is the host name or IP address of the JobTracker or Yarn resource manager. <port> is the port on which the JobTracker or Yarn resource manager listens for remote procedure calls (RPC). If the cluster uses MapR with YARN, use the value specified in the yarn.resourcemanager.address property in yarn-site.xml. You can find yarn-site.xml in the following directory on the NameNode of the cluster: /opt/mapr/hadoop/hadoop-2.5.1/etc/hadoop . MapR with MapReduce 1 supports a highly available JobTracker. If you are using MapR distribution, define the JobTracker URI in the following format: maprfs:///
Hive Warehouse Directory on HDFS	The absolute HDFS file path of the default database for the warehouse that is local to the cluster. For example, the following file path specifies a local warehouse: /user/hive/warehouse For Cloudera CDH, if the Metastore Execution Mode is remote, then the file path must match the file path specified by the Hive Metastore Service on the Hadoop cluster. For MapR, use the value specified for the hive.metastore.warehouse.dir property in hive-site.xml . You can find hive-site.xml in the following directory on the node that runs HiveServer2: /opt/mapr/hive/hive-0.13/conf .
Advanced Hive/Hadoop Properties	Configures or overrides Hive or Hadoop cluster properties in hive-site.xml on the machine on which the Data Integration Service runs. You can specify multiple properties. Select Edit to specify the name and value for the property. The property appears in the following format: <property1>=<value> Where <property1> is a Hive or Hadoop property in hive-site.xml. <value> is the value of the Hive or Hadoop property. When you specify multiple properties, &: appears as the property separator. The maximum length for the format is 1 MB. If you enter a required property for a Hive connection, it overrides the property that you configure in the Advanced Hive/Hadoop Properties. The Data Integration Service adds or sets these properties for each map-reduce job. You can verify these properties in the JobConf of each mapper and reducer job. Access the JobConf of each job from the Jobtracker URL under each map-reduce job. The Data Integration Service writes messages for these properties to the Data Integration Service logs. The Data Integration Service must have the log tracing level set to log each row or have the log tracing level set to verbose initialization tracing. For example, specify the following properties to control and limit the number of reducers to run a mapping job: mapred.reduce.tasks=2&:hive.exec.reducers.max=10
Temporary Table Compression Codec	Hadoop compression library for a compression codec class name.
Codec Class Name	Codec class name that enables data compression and improves performance on temporary staging tables.
Metastore Execution Mode	Controls whether to connect to a remote metastore or a local metastore. By default, local is selected. For a local metastore, you must specify the Metastore Database URI, Driver, Username, and Password. For a remote metastore, you must specify only the Remote Metastore URI .
Metastore Database URI	The JDBC connection URI used to access the data store in a local metastore setup. Use the following connection URI: jdbc:<datastore type>://<node name>:<port>/<database name> where <node name> is the host name or IP address of the data store. <data store type> is the type of the data store. <port> is the port on which the data store listens for remote procedure calls (RPC). <database name> is the name of the database. For example, the following URI specifies a local metastore that uses MySQL as a data store: jdbc:mysql://hostname23:3306/metastore For MapR, use the value specified for the javax.jdo.option.ConnectionUR L property in hive-site.xml . You can find hive-site.xml in the following directory on the node where HiveServer 2 runs: /opt/mapr/hive/hive-0.13/conf.
Metastore Database Driver	Driver class name for the JDBC data store. For example, the following class name specifies a MySQL driver: com.mysql.jdbc.Driver For MapR, use the value specified for the javax.jdo.option.ConnectionDriverName property in hive-site.xml . You can find hive-site.xml in the following directory on the node where HiveServer 2 runs: /opt/mapr/hive/hive-0.13/conf .
Metastore Database Username	The metastore database user name. For MapR, use the value specified for the javax.jdo.option.ConnectionUserName property in hive-site.xml . You can find hive-site.xml in the following directory on the node where HiveServer 2 runs: /opt/mapr/hive/hive-0.13/conf .
Metastore Database Password	The password for the metastore user name. For MapR, use the value specified for the javax.jdo.option.ConnectionPassword property in hive-site.xml . You can find hive-site.xml in the following directory on the node where HiveServer 2 runs: /opt/mapr/hive/hive-0.13/conf .
Remote Metastore URI	The metastore URI used to access metadata in a remote metastore setup. For a remote metastore, you must specify the Thrift server details. Use the following connection URI: thrift://<hostname>:<port> Where <hostname> is name or IP address of the Thrift metastore server. <port> is the port on which the Thrift server is listening. For MapR, use the value specified for the hive.metastore.uris property in hive-site.xml . You can find hive-site.xml in the following directory on the node where HiveServer 2 runs: /opt/mapr/hive/hive-0.13/conf .