Upgrading the Teradata Connector

Use these instructions if you are upgrading one of the connectors to a newer version (for example, if you need to upgrade Cloudera Connector Powered by Teradata from version 1.2c4 to 1.3c4).

Upgrading with CDH 5 and Cloudera Manager 5

Step 1: Distributing the Sqoop Connector Parcels

  1. In the Cloudera Manager Admin Console, click Hosts in the top navigation bar and then go to the Parcels tab. Parcels for the Sqoop connectors are listed on this page, prefixed by "SQOOP_", followed by the name of the connector.
  2. Click Download for the connectors you want to install.
  3. After the parcels have been downloaded, click Distribute to distribute and unpack the connectors on all hosts in your Hadoop cluster.
  4. After the parcels have been distributed, click Activate to make them available to the cluster. Sqoop connectors are listed as Activated on the Parcels page. You must redeploy the client configuration (Step 3) for activation to take effect.

Step 2: Deploying Client Configuration Files

  1. In the Cloudera Manager Admin Console, go to the Sqoop Client service.
  2. From the Actions menu at the top right of the service page, select Deploy Client Configuration.
  3. Click Deploy Client Configuration to confirm redeployment of the client configuration.

Upgrading 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 from the Teradata download website: http://downloads.teradata.com/download/connectivity/jdbc-driver. 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.