Utilizing TDCH in TPT Scripts via the TDCH-TPT Interface - Parallel Transporter
Teradata® Parallel Transporter Reference
- Product
- Parallel Transporter
- Release Number
- 17.10
- Published
- February 2022
- Language
- English (United States)
- Last Update
- 2023-11-29
- dita:mapPath
- abr1608578396711.ditamap
- dita:ditavalPath
- obe1474387269547.ditaval
- dita:id
- ogv1478610452101
- Product Category
- Teradata Tools and Utilities
- The TDCH-TPT interface is a bridge between TPT and TDCH. The TDCH-TPT interface extends TDCH to support Hadoop file and table transfers to TPT, and vice versa. This interface gives TPT users the ability to utilize all of the pre-existing TDCH functionality within a TPT script, and gives TDCH users the ability to utilize TPT-specific functionalities alongside TDCH.
- When a TPT job script includes the DataConnector operator alongside any of the TDCH-specific Hadoop attributes, the DataConnector operator will launch a TDCH job using those TDCH-specific Hadoop attributes supplied in the TPT script. Once TDCH has validated the attribute values and filled in defaults for any missing attributes, TDCH will submit the job to the MapReduce framework. Once the map tasks have been initialized on the nodes in the Hadoop cluster, they will connect to the DataConnector operator and begin transferring data. The HadoopProperties attribute can be used to specify one or more Hadoop properties and their values (separated by spaces) which will then be used by TPT when submitting the Hadoop command internally.
- The TDCH-TPT interface depends on the TDCH jar file. The latest certified TDCH jar file is included with the TPT installation and will be the one used by default. However, if the use of a different TDCH jar file is desired, the user can set the TDCH_JARFILE environment variable to be the fully qualified filename of the desired TDCH jar. This one will then be used instead of the included TDCH jar file.