These properties are used to configure tSnowflakeCommit running in the Standard Job framework.
The Standard tSnowflakeCommit component belongs to the Cloud family.
The component in this framework is available in all Talend products.
Basic settings
| Database |
Select a type of database from the list and click Apply. |
|
Connection Component |
Select the component that establishes the connection to the database you want to commit. |
|
Close Connection |
Select this option 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. This option is selected by default. Warning:
If this component uses a Row > Main as the incoming link in a Job, the data passing through the link will be committed row by row. In this case, do not select this option so that all the rows passing through the link can be committed. |
Advanced settings
|
tStatCatcher Statistics |
Select this check box to collect log data at the component level. |
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. |
Usage
|
Usage rule |
This component is designed to work with tSnowflakeRow, tSnowflakeBulkExec, and tSnowflakeOutputBulkExec components. When this component works with a tSnowflakeRow component with no input or output row, changes made to the database are committed by the tSnowflakeCommit component. When this component works with a tSnowflakeRow component with an input row, the tSnowflakeCommit component takes the charge of committing changes made to the database if the Commit every option of the tSnowflakeRow component is set to 0 or 1; the tSnowflakeCommit component will be ignored if the value of the Commit every option of the tSnowflakeRow component is larger than 1. |
|
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 Reading data from databases through context-based dynamic connections and 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. |