August 17, 2023

tVerticaCommit – Docs for ESB 5.x



tVerticaCommit Properties

Component family




tVerticaConnection validates the
data processed through the Job into the connected DB.


Using a unique connection, this component commits in one go a
global transaction instead of doing that on every row or every batch
and thus provides 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

Basic settings

Component list

Select the tVerticaConnection
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 >
connection to link tVerticaCommit to your Job, your data will
be commited 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

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 more information on Dynamic settings and context
variables, see Talend Studio User Guide.


This component is more commonly used with other tVertica*
components, especially with the tVerticaConnection and tVerticaRollback components.


The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User

For more information on the log4j logging levels, see the Apache documentation at



Tips and Techniques

Used together, Talend Studio and the Vertica
database create very fast and affordable data warehouse and data mart applications. For more
information about how to configure Talend Studio to connect to
Vertica, see Talend and HP Vertica Tips and Techniques.

Related scenario

For tVerticaCommit related scenario, see Scenario 1: Inserting data in mother/daughter tables

Document get from Talend
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x