tELTMap - 7.3


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
Talend Studio
Data Governance > Third-party systems > ELT components > ELT JDBC components
Data Quality and Preparation > Third-party systems > ELT components > ELT JDBC components
Design and Development > Third-party systems > ELT components > ELT JDBC components
Last publication date

Uses the tables provided as input to feed the parameter in the built SQL statement. The statement can include inner or outer joins to be implemented between tables or between one table and its aliases.

Warning: The query order of the built SQL statement is generated the same way as it appears in the GUI, so having the LEFT JOIN clauses prior to the INNER JOIN clauses could result in data loss. However, Talend has no plan to change this behavior from the GUI at this time, as some databases like PostgreSQL consider the query order when generating the execution plan and the order part is necessary for query runtime optimization.

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.

For more technologies supported by Talend, see Talend components.

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.