tPostgresqlOutputBulkExec – Docs for ESB 5.x

Component family

Databases/Postgresql

Function

Executes the Insert action on the data provided.

Purpose

As a dedicated component, it allows gains in performance during
Insert operations to a Postgresql 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.

DB Version

List of database versions.

Host

Database server IP address.

Currently, only localhost,
127.0.0.1 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
tPostgresqlOutputBulkExec is
deployed.

Port

Listening port number of DB server.

Database

Name of the database

Schema

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.

Table

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
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 a table: The table content is
deleted.

File Name

Name of the file to be generated and loaded.

Schema and Edit
Schema

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

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 https://help.talend.com/display/KB/Verifying+default+values+in+a+retrieved+schema.

Advanced settings

Action on data

On the data of the table defined, you can perform:

Bulk Insert: Add multiple entries
to the table. If duplicates are found, job stops.

Bulk Update: Make simultaneous
changes to multiple entries.

Copy the OID for each row

Retrieve the ID item for each row.

Contains a header line with the names of each column in
the file

Specify that the table contains header.

Encoding

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

File type

Select the type of file being handled.

Null string

String displayed to indicate that the value is null..

Row separator

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

Fields terminated by

Character, string or regular expression to separate fields.

Escape char

Character of the row to be escaped.

Text enclosure

Character used to enclose text.

Activate standard_conforming_string

Activate the variable.

Force not null for columns

Define the columns nullability.

Force not null: Select the check
box next to the column you want to define as not null.

tStatCatcher Statistics

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

Enable parallel execution

Select this check box to perform high-speed data processing, by treating multiple data flows
simultaneously. Note that this feature depends on the database or the application ability to
handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either:

Note that when parallel execution is enabled, it is not possible to use global variables to
retrieve return values in a subjob.

Usage

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