Shared Content for Data Engineering
All Products
Option | Description |
---|---|
connectionType | Required. Type of connection is HIVE. |
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: ~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? / |
relationalSourceAndTarget | Hive connection mode. Set this option to true if you want to use the connection to access the Hive data warehouse. If you want to access Hive target, you need to enable the same connection or another Hive connection to run the mapping in the Hadoop cluster. If you enable relational source and target, you must provide the metadataDatabaseString option. |
pushDownMode | Hive connection mode. Set this option to true if you want to use the connection to run mappings in the Hadoop cluster. If you enable the connection for pushdown mode, you must provide the options to run the Informatica mappings in the Hadoop cluster. |
environmentSQL | 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 Hive metastore. If the Hive connection is used to run mappings 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 the connection modes:
If the Hive connection is used to run mappings in the Hadoop cluster, only the environment SQL of the Hive connection is executed. The different environment SQL commands for the connections of the Hive source or target are not executed, even if the Hive sources and targets are on different clusters. |
enableQuotes | Encloses all database reserved words in quotes. Default is false. |
Property | Description |
---|---|
metadataConnString | The JDBC connection URI used to access the metadata from the Hadoop server. The connection string uses the following format: jdbc:hive://<hostname>:<port>/<db> Where
|
bypassHiveJDBCServer | JDBC driver mode. Enable this option to use the embedded JDBC driver (embedded mode). To use the JDBC embedded mode, perform the following tasks:
If you choose the non-embedded mode, you must configure the Data Access Connection String. The JDBC embedded mode is preferred to the non-embedded mode. |
connectString | The connection string used to access data from the Hadoop data store. The non-embedded JDBC mode connection string must be in the following format: jdbc:hive://<hostname>:<port>/<db> Where
|
Property | Description |
---|---|
databaseName | Namespace for tables. Use the name default for tables that do not have a specified database name. |
defaultFSURI | The URI to access the default Hadoop Distributed File System. The FS URI must be in the following format: hdfs://<node name>:<port> Where
|
jobTrackerURI | The service within Hadoop that submits the MapReduce tasks to specific nodes in the cluster. JobTracker URI must be in the following format: <jobtrackername>:<port> Where
|
hiveWarehouseDirectoryOnHDFS | The absolute HDFS file path of the default database for the warehouse, which is local to the cluster. For example, the following file path specifies a local warehouse: /user/hive/warehouse |
metastoreExecutionMode | Controls whether to connect to a remote metastore or a local metastore. 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 . |
metastoreDatabaseURI | The JDBC connection URI used to access the data store in a local metastore setup. The URI must be in the following format: jdbc:<datastore type>://<node name>:<port>/<database name> where
For example, the following URI specifies a local metastore that uses MySQL as a data store: jdbc:mysql://hostname23:3306/metastore |
metastoreDatabaseDriver | Driver class name for the JDBC data store. For example, the following class name specifies a MySQL driver: com.mysql.jdbc.Driver |
metastoreDatabaseUserName | The metastore database user name. |
metastoreDatabasePassword | The password for the metastore user name. |
remoteMetastoreURI | The metastore URI used to access metadata in a remote metastore setup. For a remote metastore, you must specify the Thrift server details. The URI must be in the following format: thrift://<hostname>:<port> Where
|
Updated April 22, 2019