Action on data

On the data of the table defined, you can
perform the following operation:

Insert: Add new entries
to the table. If duplicates are found, Job stops.

Update: Updates entries
in the table.

Delete: Deletes the
entries which correspond to the entry flow.

Schema 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.

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.

Built-in: The schema is
created and stored locally for this component only. Related topic: see
Talend Studio
User Guide.

Repository: The schema
already exists and is stored in the Repository, hence can be reused. Related
topic: see
Talend Studio
User Guide.

Where clauses for (for UPDATE and
DELETE only)

Enter a clause to filter the data to be updated
or deleted during the update or delete operations.

Default Table Name

Enter a default name for the table, between
double quotation marks.

Note that the table must exist already. If it
does not exist, you can use tCreateTable to create one
first. For more information about tCreateTable, see tCreateTable.

Table name from connection name is
variable

Select this check box when the name of the connection to this
component is set to a variable, such as a context variable.

Use different table name

Select this check box to enter a different
output table name, between double quotation marks, in the Table name field which
appears.

Mapping

Specify the metadata mapping file
for the database to be used. The metadata mapping file is used for the data
type conversion between database and Java. For more information about the
metadata mapping, see the related documentation for Type mapping.

Select the column names that will be used to generate the SET
clauses.

SET clauses will not be generated for the columns that are not selected.

This field appears when Update is
selected from the Action on data drop-down list in the
Basic settings view.

tStatCatcher Statistics

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

Global Variables

NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an
integer.

NB_LINE_INSERTED: the number of rows inserted. 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

tELTTeradataOutput is to
be used along with the tELTTeradataMap. Note that the Output link to be used with
these components must correspond strictly to the syntax of the table name.

Due to license incompatibility, one or more JARs required to use
this component are not provided. You can install the missing JARs for this particular
component by clicking the Install button
on the Component tab view. You can also
find out and add all missing JARs easily on the Modules tab in the
Integration
perspective of your studio. You can find more details about how to install external modules in
Talend Help Center (https://help.talend.com).