July 30, 2023

tELTInput – Docs for ESB 7.x

tELTInput

Adds as many Input tables as required for the SQL statement to be
executed.

The three ELT components are closely related, in terms of
their operating conditions. These components should be used to handle DB schemas to
generate Insert statements, including clauses, which are to be executed in the DB output
table defined.

Note that it is highly recommended to use
the ELT components for a specific type of database (if any) instead of the ELT
components. For example, for Teradata, it is recommended to use the tELTTeradataInput, tELTTeradataMap and tELTTeradataOutput components instead.

tELTInput Standard properties

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

The Standard
tELTInput component belongs to the ELT
family.

The component in this framework is available in all Talend
products
.

Basic settings

Schema and Edit
schema

A schema is a row description, it defines the nature and number
of fields to be processed. The schema is either built-in or remotely stored in
the Repository. The Schema defined is then passed on to the ELT Mapper to be
included to the Insert SQL statement.

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
.

Default Table Name

Type in the default table name.

Default Schema Name

Type in the default schema name.

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.

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

User Guide.

Usage

Usage rule

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

Note:

Note that the ELT components do not handle actual data flow but only schema
information.


Document get from Talend https://help.talend.com
Thank you for watching.
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x