tParAccelOutputBulkExec Properties - 6.1

Talend Components Reference Guide

English (United States)
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
Talend Studio
Data Governance
Data Quality and Preparation
Design and Development

The tParAccelOutputBulk and tParAccelBulkExec components 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.

Component Family




tParAccelOutputBulkExec performs an Insert action on the data.


tParAccelOutputBulkExec is a component which is specifically designed to improve performance when loading data in ParAccel database.

Basic settings

Property type

Either Built-in or Repository.

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 centrally.



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 deployed.



Listening port number of the DB server.



Database name.



Exact name of the schema.


Username and Password

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 operations:

None: No operation is carried out.

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 deleted.


Schema and Edit Schema

A schema is a row description. It defines the number of fields (columns) 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.



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


Click Edit schema 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] window.


Copy mode

Select the copy mode you want to use from either:

Basic: Standard mode, without optimisation.

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

File Type

Select the file type from the list.


Row separator

String (ex: "\n"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 file.


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 use.


Log file

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


Logging level

Select the information type you want to record in your log file.


tStat Catcher Statistics

Select this check box to collect log data at the component level.


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 Scenario 3: Retrieve 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.