The three ELT JDBC components are closely related, in terms of their operating conditions. These components should be used to handle JDBC DB schemas to generate Insert statements, including clauses, which are to be executed in the DB output table defined.
|
Function |
Carries out the action on the table specified and inserts the data according to the output schema defined the ELT Mapper. | |
|
Purpose |
Executes the SQL Insert, Update and Delete statement to the JDBC database | |
|
Component family |
ELT/Map/JDBC | |
|
Basic settings |
Action on data |
On the data of the table defined, you can perform the following operation: Insert: Adds 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 to be processed and passed on to the next component. The schema is either built-in or remotely stored in the Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
|
|
|
|
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 the default table name, between double quotation marks. |
|
|
Default Schema Name |
Enter the default schema name,between double quotation marks. |
|
|
Use different table name |
Select this check box to define a different output table name, between double quotation marks, in the Table name field which appears. |
|
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 |
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 |
tELTJDBCOutput 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. NoteNote that the ELT components do not handle actual data flow but only schema information. | |
|
Log4j |
If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide. For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html. | |
For use cases in relation with tELTJDBCOutput, see tELTMysqlMap scenarios: