tELTTeradataUniteMap Standard properties - Cloud - 8.0

ELT Teradata

Version
Cloud
8.0
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > ELT components > ELT Teradata components
Data Quality and Preparation > Third-party systems > ELT components > ELT Teradata components
Design and Development > Third-party systems > ELT components > ELT Teradata components
Last publication date
2024-02-20

These properties are used to configure tELTTeradataUniteMap running in the Standard Job framework.

The Standard tELTTeradataUniteMap component belongs to the ELT family.

The component in this framework is available in all subscription-based Talend products.

Note: This component is available only when you have installed the 8.0.1-R2023-03 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator.

Basic settings

Use an existing connection

Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.

Note: When a Job contains the parent Job and the child Job, do the following if you want to share an existing connection between the parent Job and the child Job (for example, to share the connection created by the parent Job with the child Job).
  1. In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.
  2. In the child level, use a dedicated connection component to read that registered database connection.

For an example about how to share a database connection across Job levels, see Sharing a database connection.

ELT Teradata Map editor

The ELT Map editor allows you to define the output schema and make a graphical build of the SQL statement to be executed. It also allows you to specify the operation to be carried out against the result sets of the SQL SELECT statements generated by the tELTTeradataMap components connecting to it.
Note:
  • The column names of schema can be different from the column names in the database.
  • The input and output tables must have the same number of columns.

This component requires two or multiple input tables. You can add an input table by clicking the plus button on the upper left corner of the ELT Map editor, selecting the desired table from the Table drop-down list in the Add input table dialog box, and clicking OK. You also need to specify the operation to be carried out against the result sets of the SQL SELECT statements generated by the tELTTeradataMap components by selecting the operation from the menu on the title bars of the second input table and the subsequent input tables (if any). You can select the following operations from the menu.

  • UNION
  • UNION ALL
  • INTERSECT
  • MINUS
  • EXCEPT

You can filter schema columns in an input or output table by clicking the Enable/disable column name filter button in the corresponding table and entering the search keyword in the field displayed.

Style link

Select the way in which links are displayed.

Auto: By default, the links between the input and output schemas and the Web service parameters are in the form of curves.

Bezier curve: Links between the schema and the Web service parameters are in the form of curve.

Line: Links between the schema and the Web service parameters are in the form of straight lines.

This option slightly optimizes performance.

Property type

Either Built-in or Repository.

  • Built-in: No property data stored centrally.
  • Repository: Select the Repository file where Properties are stored. The following fields are pre-filled in using fetched data.

Host

Database server IP address

Database

Name of the database

Username and Password

DB user authentication data.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Mapping

Automatically set mapping parameter.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a Job level as well as at each component level.

Global Variables

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.

Usage

Usage rule

This component requires two or multiple tELTTeradataMap components as the input. The output data is passed to a tELTTeradataOutput component. Note that the Output link to be used with these components must correspond strictly to the syntax of the table name.

Note: The ELT components do not handle actual data flow but only schema information.

Dynamic settings

Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your database connection dynamically from multiple connections planned in your Job. This feature is useful when you need to access database tables having the same data structure but in different databases, especially when you are working in an environment where you cannot change your Job settings, for example, when your Job has to be deployed and executed independent of Talend Studio.

The Dynamic settings table is available only when the Use an existing connection check box is selected in the Basic settings view. Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Dynamic schema and Creating a context group and define context variables in it.