July 30, 2023

tParAccelOutputBulkExec – Docs for ESB 7.x


Improves performance when loading data in ParAccel

The tParAccelOutputBulk and tParAccelBulkExec are generally used together in 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 tParAccelOutputBulkExec.

The tParAccelOutputBulkExec performs
an Insert action on the data.

tParAccelOutputBulkExec Standard properties

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

The Standard
tParAccelOutputBulkExec component belongs to the Databases family.

The component in this framework is available in all Talend

Note: This component is a specific version of a dynamic database
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.

Basic settings


Select a type of database from the list and click

Property type

Either Built-in or


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.


Database server IP address.

Currently, only localhost, or the exact IP
address of the local machine is allowed for proper functioning. In
other words, the database server must be installed on the same
machine where the Studio is installed or where the Job using
tParAccelOutputBulkExec is


Listening port number of the DB server.


Database name.


Exact name of the schema.

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

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 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
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the


Built-In: You create and store the schema locally for this component


Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

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.

You can find more details about how to
verify default values in retrieved schema in Talend Help Center (https://help.talend.com).


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

  • 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 changes.

  • 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 Content

Copy mode

Select the copy mode you want to use from either:

Basic: Standard mode, without

Parallel: Allows you to use several
internal ParAccel APIs in order to optimise loading speed.


Name of the file to be generated and loaded.


This file is generated on the machine specified by the URI in
the Host field so it should be
on the same machine as the database server.

Advanced settings

Additional JDBC Parameters

Specify additional JDBC parameters for the
database connection created.

File Type

Select the file type from the list.

Row separator

String (ex: ”
“on Unix) to distinguish rows.

Fields terminated by

Character, string or regular expression to separate fields.


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

Explicit IDs

The ID is already present in the file to be loaded or will be set
by the database.

Remove Quotes

Select this check box to remove quotation marks from the file to
be loaded.

Max. Errors

Type in the maximum number of errors before your Job stops.

Date Format

Type in the date format to be used.

Time/Timestamp Format

Enter the date and hour format to be used.

Additional COPY Options

Enter the specific, customized ParAccel option that you want to

Log file

Browse to or enter the access path to the log file in your

Logging level

Select the information type you want to record in your log

Catcher Statistics

Select this check box to collect log data at the component


Usage rule

This component covers all possible SQL database queries. It allows
you to carry out actions on a table or on the data of a table in a
ParAccel database. It enables you to create a reject flow, with a
Row > Reject link filtering the data in error. For a usage
example, see Retrieving data in error with a Reject link.


The database server must be installed on the same machine where
the Studio is installed or where the Job using tParAccelOutputBulkExec is deployed, so that the
component functions properly.

Related scenarios

For related scenarios, see:

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