tGreenplumOutputBulkExec – Docs for ESB 5.x

Component family

Databases/Greenplum

Function

Executes the action on the data provided.

Purpose

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

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

Port

Listening port number of DB server.

Database name

Name of the database.

Schema

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.

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 a table: The table
is removed and created again.

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

Create a 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 a table: The table content is
deleted. You have the possibility to rollback the operation.

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.

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.

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

Advanced settings

Action on data

Select the operation you want to perform:

Bulk insert Bulk update The details asked will be different
according to the action chosen.

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.

File type

Select the file type to process.

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.

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.

tStatCatcherStatistics

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

Usage

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

Limitation

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