Prerequisites for Teradata Connector

To use the Cloudera Connector Powered by Teradata, you must have a functioning CDH installation, including Sqoop components. Depending on how Sqoop is installed, you may need administrative privileges to create or modify configuration files.

The Teradata connector uses catalog tables and views to look up metadata information. Therefore, the user making the connection must have the SELECT privilege on the DBC database. Check with your Teradata administrators or operators if you are not sure whether you have the required privileges. You must have SELECT privileges on at least one of the following DBC database object types:

  • DBC.columns
  • DBC.databases
  • DBC.tables
  • DBC.indices

Depending on the input method used, the Teradata connector might need to create temporary tables or temporary views to import data. Check with your Teradata administrators or operators to determine if you have the required privileges.

The Cloudera Connector Powered by Teradata requires the following additional permissions to use *.fastload data methods.
  • DBC.table_levelconstraints
  • DBC.triggers
  • DBC.tvm
  • DBC.dbase
  • DBC.referencingtbls

For more information about how to install, configure, and use Sqoop, see the Sqoop documentation in the CDH 5 Installation Guide.

Cloudera Connector powered by Teradata version 1.7c6

  • Teradata 13.00 and higher
  • CDH 6.0 and higher
  • Sqoop 1.4 and higher, but not compatible with Sqoop2

Cloudera Connector powered by Teradata versions 1.2c5, 1.3c5, 1.4c5, 1.5c5, 1.6c5, 1.7c5

  • Teradata 13.00 and higher
  • All CDH 5 releases
  • Sqoop 1.4 and higher, but not compatible with Sqoop2

Cloudera Connector powered by Teradata versions 1.0.0, 1.2c4, 1.3c4, 1.4c4

  • Teradata 13.00 and higher
  • CDH 4.2 and higher in CDH 4
  • Sqoop 1.4 and higher, but not compatible with Sqoop2