Function |
tVectorWiseCommit validates the data processed in a Job into the connected DB. | |
Purpose |
Using a single connection, this component commits a global transaction in one go instead of doing so on every row or every batch. This provides a gain in performance Note that if you need to commit each statement as an individual transaction, you have to use the Auto Commit function available in the connection component. |
Component family |
Databases/VectorWise | |
Basic settings |
Component list |
Select the tVectorWiseConnection component from the list if more than one connection is 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. WarningIf you want to use a Row > Main connection to link tVectorWiseCommit 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 |
tStatCatcher Statistics |
Select this check box to collect log data at the component level. |
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. 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 3: Reading data from MySQL 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 |
This component is more commonly used with other tVectorWise* components, especially with the tVectorWiseConnection and tVectorWiseRollback components. | |
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. | |
Limitation |
n/a |
For a tVectorWiseCommit related scenario, see Scenario 1: Inserting data in mother/daughter tables.