tParAccelCommit Standard properties


Talend Documentation Team
Talend ESB
Talend Open Studio for Big Data
Talend Data Management Platform
Talend Open Studio for Data Integration
Talend Data Services Platform
Talend MDM Platform
Talend Open Studio for MDM
Talend Open Studio for ESB
Talend Big Data Platform
Talend Real-Time Big Data Platform
Talend Big Data
Talend Data Fabric
Talend Data Integration
Design and Development > Third-party systems > Database components > ParAccel components
Data Quality and Preparation > Third-party systems > Database components > ParAccel components
Data Governance > Third-party systems > Database components > ParAccel components
Talend Studio

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

The Standard tParAccelCommit component belongs to the Databases family.

The component in this framework is available in all Talend products.

Basic settings

Component list

Select the tParAccelConnection 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.


If you want to use a Row > Main connection to link tParAccelCommit 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 rule

This component is more commonly used with other tParAccel* components, especially with the tParAccelConnection and tParAccelRollback 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.