Installing the Teradata Connector

Use one of the following methods to install the Sqoop connector for Teradata:

Installation with CDH 5 and Cloudera Manager 5

Step 1: Adding the Sqoop Client Gateway

The Sqoop1 Client Gateway sets up and manages the connector configuration for the hosts where you execute Sqoop1 commands. If you do not already have the Sqoop1 Client Gateway deployed in your cluster, deploy it before proceeding.

Step 2: Download, Distribute, and Activate the Sqoop Parcels

Parcels for Sqoop connectors are prefixed by SQOOP_, followed by the name of the connector.

Follow the instructions in Managing Parcels to download, distribute, and activate Sqoop parcels.

Installation without Cloudera Manager

  1. Install the Sqoop connector by opening the distribution archive in a convenient location such as /usr/lib. Opening the distribution creates a directory that contains the jar file of the compiled version of the connector. Note the path to this jar file. The directory that is created when the file is expanded varies according to which connector you are using. Examples of typical resulting paths include:
    • Cloudera Connector Powered by Teradata 1.2cX: /usr/lib/sqoop-connector-teradata-1.2cX/sqoop-connector-teradata-1.2cX.jar
  2. Copy the Teradata JDBC drivers (terajdbc4.jar and tdgssconfig.jar) to the lib directory of the Sqoop installation. You can obtain these drivers by extracting them from the Teradata Connector JAR that you downloaded from: https://www.cloudera.com/downloads/connectors/sqoop/teradata/1-2c5.html. Without these drivers, the connector will not function correctly.
  3. Confirm that the managers.d directory exists in the Sqoop configuration directory. If the managers.d directory does not exist, create it and ensure that the directory permissions are set to 755.
  4. Create a text file in the managers.d directory with a descriptive name such as cldra_td_connector. Ensure the file permissions are set to 644.
  5. The cldra_td_connector file must have the connector class name followed by the complete path to the directory where the connector jar is located.
    For example, for the Cloudera Connector powered by Teradata 1.2cX:
    com.cloudera.connector.teradata.TeradataManagerFactory= \
    /usr/lib/sqoop-connector-teradata-1.2cX/sqoop-connector-teradata-1.2cX.jar

    TeradataManagerFactory acts as a single point of delegation for invoking the connector bundled with this distribution. Alternatively, you can specify TeradataManagerFactory inside a sqoop-site.xml file, which must be inside a classpath directory.

    If you are using Cloudera Connector powered by Teradata, use the following:

    <configuration>
      <property>
        <name>sqoop.connection.factories</name>
        <value>com.cloudera.connector.teradata.TeradataManagerFactory</value>
      </property>
    <configuration>

    This configures a Sqoop action to use the Teradata connector inside Oozie.