August 17, 2023

tVerticaOutputBulkExec – Docs for ESB 5.x



tVerticaOutputBulkExec Properties

The tVerticaOutputBulk and tVerticaBulkExec components are generally used together as parts of a
two step process. In the first step, an output file is generated. In the second step,
this file is used in the INSERT operation used to feed a database. These two steps are
fused together in the tVerticaOutputBulkExec

Component family




tVerticaOutputBulkExec executes
the Insert action on the data provided.


As a dedicated component, it allows gains in performance during
Insert operations to a Vertica database.

Basic settings

Property Type

Either Built-in or

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.



Built-in: No property data stored



Repository: Select the repository
file in which the properties are stored. The fields that follow are
completed automatically using the data retrieved.


DB Version

Select the version of Vertica you are using from the list.


Use existing connection

Select this check box and in the Component List click the
relevant connection component to reuse the connection details you already defined.



Database server IP address.



Listening port number of DB server.


DB Name

Name of the database


Username and

DB user authentication data.

To enter the password, click the […] button next to the
password field, and then in the pop-up dialog box enter the password between double quotes
and click OK to save the settings.



Name of the table to be written. Note that only one table can be
written at a time and that the table must exist for the insert
operation to succeed.


Action on table

On the table defined, you can perform one of the following

None: No operation is carried

Drop and create table: The table is
removed and created again.

Create table: The table does not
exist and gets created.

Create table if not exists: The
table is created if it does not exist.

Drop table if exists and create:
The table is removed if it already exists and created again.

Clear table: The table content is


Schema and Edit

A schema is a row description. It defines the number of fields to be processed and passed on
to the next component. The schema is either Built-In or
stored remotely in the Repository.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are

  • View schema: choose this option to view the
    schema only.

  • Change to built-in property: choose this option
    to change the schema to Built-in for local

  • Update repository connection: choose this option to change
    the schema stored in the repository and decide whether to propagate the changes to
    all the Jobs upon completion. If you just want to propagate the changes to the
    current Job, you can select No upon completion and
    choose this schema metadata again in the [Repository



Built-In: You create and store the schema locally for this
component only. Related topic: see Talend Studio
User Guide.



Repository: You have already created the schema and
stored it in the Repository. You can reuse it in various projects and Job designs. Related
topic: see Talend Studio User Guide.

When the schema to be reused has default values that are integers or functions, ensure that
these default values are not enclosed within quotation marks. If they are, you must remove
the quotation marks manually.

For more details, see


File Name

Name of the file to be generated and loaded.

This file is generated on the same machine where the Studio is
installed or where the Job using tVerticaOutputBulkExec is deployed.



Select this check box to add the new rows at the end of the

Advanced settings

Additional JDBC Parameters

Specify additional JDBC parameters for the database connection
being created.

This option is not available when the Use an
existing connection
check box in the Basic settings tab is selected.

Write to ROS (Read Optimized Store)

Select this check box to store the data in a physical storage
area, in order to optimize the reading, as the data is compressed
and pre-sorted.


Exit job if no row was loaded

The Job automatically stops if no row has been loaded.


Field Separator

Character, string or regular expression to separate fields.


Null string

String displayed to indicate that the value is null.


Include header

Select this check box to include the column header to the file.



Select the encoding from the list or select Custom and define it manually. This field is
compulsory for DB data handling.


Rejected data file

Specify a file you want to write rejected rows to.


Exception log file

Specify a file you want to write an explanation for each rejected
row to.


tStatCatcher Statistics

Select this check box to collect log data at the component

Global Variables

ACCEPTED_ROW_NUMBER: the number of rows loaded into the

REJECTED_ROW_NUMBER: the number of rows rejected.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio
User Guide.


This component is mainly used when no particular transformation is
required on the data to be loaded onto the database.


Due to license incompatibility, one or more JARs required to use this component are not
provided. You can install the missing JARs for this particular component by clicking the
Install button on the Component tab view. You can also find out and add all missing JARs easily on
the Modules tab in the Integration perspective
of your studio. For details, see
or the section describing how to configure the Studio in the Talend Installation and Upgrade

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 scenarios

For use cases in relation with tVerticaOutputBulkExec, see the following scenarios:

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