Table of Contents

Search

  1. Preface
  2. Mappings
  3. Mapplets
  4. Mapping Parameters
  5. Where to Assign Parameters
  6. Mapping Outputs
  7. Generate a Mapping from an SQL Query
  8. Dynamic Mappings
  9. How to Develop and Run a Dynamic Mapping
  10. Dynamic Mapping Use Cases
  11. Mapping Administration
  12. Import From PowerCenter
  13. Performance Tuning
  14. Pushdown Optimization
  15. Partitioned Mappings
  16. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Teradata Data Object Example

Teradata Data Object Example

A Teradata data object represents metadata based on a Teradata resource.
When you configure a data object read operation for the Teradata data object and view it in the object editor, you can see a source object and an output object. The output object displays the metadata from the Teradata resource.
The following image shows a data object read operation for the Teradata data object:
The image shows a Teradata data object with a read operation. The object editor shows a source object and an output object in the object editor. The source object is connected directly to the downstream output object. The metadata from the Teradata resource is in the output object.
The source object is
tpt_src
and the output object is
Output
. The source and output objects comprise the data object read operation.
You can look at the metadata in the output object and see that the native data types in
tpt_src
are converted into transformation data types in the output object. For example, the native data type VARCHAR for the
name
port is converted to the transformation data type string.
To use the Teradata data object in a mapping, you can create a Read transformation. When you add the Read transformation to the mapping, you select the Teradata data object and the data object read operation that you previously configured.
Because the Read transformation needs to access the transformation data types stored in the output object of the data object read operation, the Read transformation is created based on the object operation, not the Teradata data object. The Read transformation uses the same properties that you configured for the data object read operation.
The following image highlights the Read transformation
tpt_read
in the mapping editor:
The image shows a Teradata data object with a Read transformation in the mapping editor. In this example, the Read transformation is connected directly to an associated downstream Write transformation. The metadata in the Read transformation is the same as the metadata in the output object shown in the data object editor in the previous image.
Notice that the metadata in the Read transformation and the output object of the data object read operation are the same. For example, the metadata in the
name
port uses the transformation data type string instead of the native data type VARCHAR.

0 COMMENTS

We’d like to hear from you!