Connections using BDA enable loading data into Hive as a target database and they also enable loading data from Hive into Datawarehouse tables as a source, using the Apache Sqoop load method.
This connection type needs to include the JDBC connection string (JDBC URL) and related attributes (username, password) for the Hive database. The JDBC User and Password is usually the same as the Extract User ID but users can specify different credentials if necessary.
The Big Data Adapter settings will also need to be populated in the Datawarehouse connection. Refer to Database - the Data Warehouse/Metadata Repository for details.
RED can also load data directly into Hive from any database source. This load can also be processed via an Apache Sqoop load and the JDBC settings on the Hive connection will need to be populated. Please see the connection example and field description below for more details about this. When loading data into Hive as a target, users can also add specific target locations in their Hive ODBC connections, if they have a Hive target license enabled.
Hive connection properties will be the same for any database sources.
Example of a Hive ODBC connection
Big Data Adapter Settings
Options | Description |
|---|---|
Big Data Adapter Host | Host machine on which the Big Data Adapter is running its web-server. |
Big Data Adapter Port | Port that Tomcat is running. Default is 8080. |
Base Target Directory for Sqoop Loads | HDFS directory in which to create target directories for Sqoop loads using the Big Data Adapter. |
JDBC Connection String (JDBC URL) | Connection string used by the WhereScape Big Data Adapter to access this database. |
JDBC Driver Class Name | JDBC driver class to be used by the WhereScape Big Data Adapter. This field must be set if the JDBC URL is set. Select the appropriate JDBC Driver class name from the drop-down list. If this is left empty this will not be specified in generated commands. |
Omit Sqoop Driver Option | If set, the --driver option to Sqoop is omitted. This is required for certain connection types such as Oracle connections. If you select the Omit Sqoop Driver Option check box, the driver parameter is not used in the Sqoop command line. This is a requirement for Oracle at the moment, as suggested by Sqoop documentation for 1.4.5. |
Sqoop Connection Manager Class | Custom Sqoop connection manager class. Corresponds to the --connection-manager command line argument. Leave blank if this is not required. The full JDBC connection string is:
|
