tTeradataCDC Standard properties

Select a type of database from the list and click Apply.

Property of the CDC connection

Either Built-In or Repository.

Built-In: No property data stored centrally.

Repository: Select the repository file in which the properties are stored. The database connection related fields that follow are completed automatically using the data retrieved.

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.

Host

Type in the IP address or hostname of the database.

Database

Type in the name of the database you want to use.

Username and Password

Type in the database user authentication data.

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

Schema using CDC and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

The schema of this component is set by default.

Built-In: You create and store the schema locally for this component only.

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Table using CDC

Specify the name of the table from which data changes will be captured.

Subscriber

Specify the name of the application that will use the change table in Trigger mode.

Events to catch

Insert: Select this check box to catch the data inserted in the change table since the last extraction.

Update: Select this check box to catch the data updated in the change table since the last extraction.

Delete: Select this check box to catch the data deleted in the change table since the last extraction.

Additional JDBC Parameters

Specify additional connection properties for the database connection you are creating.

This field is not visible when the Use an existing connection check box is selected.

Keep data in CDC Table

Select this check box to keep the changes made available to one or more target systems, even after they have been consulted.

Trim all the String/Char columns

Select this check box to remove the leading and trailing whitespaces from all the String/Char columns.

Trim column

Select the check box(es) in the Trim column to remove the leading and trailing whitespaces from the corresponding column(s).

This table is not visible when the Trim all the String/Char columns check box is selected.

tStatCatcher Statistics

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

Global Variables

NB_LINE: the number of rows processed. This is an After variable and it returns an integer.

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 further information about variables, see Talend Studio User Guide.

Usage rule

This component is usually used as a start component of a Job or subJob and it needs an output link.