tRedshiftCommit

Provides gain in performance.

Using a unique connection, this component commits in one go a global transaction instead of doing that on every row or every batch.

tRedshiftCommit validates the
data processed through the Job into the connected database.

tRedshiftCommit Standard properties

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

The Standard
tRedshiftCommit component belongs to the Cloud and the Databases families.

The component in this framework is generally available.

Basic settings

Component list	Select the tRedshiftConnection component in the list if more than one connection are planned for the current job.
Close Connection	This check box is selected by default. It allows you to close the database connection once the commit is done. Clear this check box to continue to use the selected connection once the component has performed its task. Warning: If you want to use a Row > Main connection to link tRedshiftCommit to your Job, your data will be committed row by row. In this case, do not select the Close Connection check box or your connection will be closed before the end of your first row commit.

Component list

Select the tRedshiftConnection
component in the list if more than one connection are planned for
the current job.

Close Connection

This check box is selected by default. It allows you to close the
database connection once the commit is done. Clear this check box to
continue to use the selected connection once the component has
performed its task.

Warning:

If you want to use a Row
>

Main
connection to link tRedshiftCommit to your Job, your data will
be committed row by row. In this case, do not select the
Close Connection check
box or your connection will be closed before the end of your
first row commit.

Advanced settings

tStat Catcher Statistics	Select this check box to collect log data at the component level.

Usage

Usage rule	This component is more commonly used with other tRedshift* components, especially with the tRedshiftConnection and tRedshiftRollback components.
Dynamic settings	Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your database connection dynamically from multiple connections planned in your Job. This feature is useful when you need to access database tables having the same data structure but in different databases, especially when you are working in an environment where you cannot change your Job settings, for example, when your Job has to be deployed and executed independent of Talend Studio . Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable. For examples on using dynamic parameters, see Scenario: Reading data from databases through context-based dynamic connections and Scenario: Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Talend Studio User Guide.

Usage rule

This component is more commonly used with other tRedshift*
components, especially with the tRedshiftConnection and tRedshiftRollback components.

Dynamic settings

Click the [+] button to add a
row in the table and fill the Code field
with a context variable to choose your database connection dynamically from
multiple connections planned in your Job. This feature is useful when you
need to access database tables having the same data structure but in
different databases, especially when you are working in an environment where
you cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of
Talend Studio
.

Once a dynamic parameter is defined, the Component List box in the Basic
settings view becomes unusable.

For examples on using dynamic parameters, see Scenario: Reading data from databases through context-based dynamic connections and Scenario: Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic
settings and context variables, see
Talend Studio User Guide.

Related scenario

For a similar scenario, see Scenario: Inserting data in mother/daughter tables.

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 6.x

0 Comments

Inline Feedbacks

View all comments

tRedshiftCommit – Docs for ESB 6.x