The tGreenplumOutputBulk and tGreenplumBulkExec components are 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 statement used to feed a database. These two steps are fused together in the
tGreenplumOutputBulkExec component, detailed in a
separate section. The advantage using a two step process is that it makes it possible to
transform data before it is loaded in the database.
Component Family |
Databases/Greenplum |
|
Function |
tGreenplumBulkExec performs an |
|
Purpose |
tGreenplumBulkExec |
|
Basic settings |
Property type |
Either Built-in or Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-in: No property data stored |
|
|
Repository: Select the repository |
|
Use an existing connection |
Select this check box and in the Component List click the NoteWhen a Job contains the parent Job and the child Job, if you need to share an existing
For an example about how to share a database connection across Job levels, see |
|
Host |
Database server IP address. |
|
Port |
Listening port number of DB server. |
|
Database |
Name of the database. |
|
Schema |
Exact name of the schema. |
|
Username and |
DB user authentication data. To enter the password, click the […] button next to the |
|
Table |
Name of the table to be written. Note that only one table can be |
|
Action on table |
On the table defined, you can perform one of the following
None: No operation is carried
Drop and create a table: The table
Create a table: The table does not
Create a table if not exists: The
Drop a table if exists and create:
Clear a table: The table content is |
|
Filename |
Name of the file to be loaded. WarningThis file is located on the machine specified by the URI in |
|
Schema and Edit |
A schema is a row description. It defines the number of fields to be processed and passed on Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-In: You create and store the schema locally for this |
|
|
Repository: You have already created the schema and When the schema to be reused has default values that are integers or functions, ensure that 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
|
||
Advanced settings |
Action on data |
Select the operation you want to perform:
Bulk insert Bulk update The details asked will be different |
|
Copy the OID for each row |
Retrieve the ID item for each row. |
|
Contains a header line with the names of each column in |
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. |
|
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 |
|
tStat |
Select this check box to collect log data at the component |
Dynamic settings |
Click the [+] button to add a row in the table and fill The Dynamic settings table is available only when the For more information on Dynamic settings and context |
|
Usage |
This component is generally used with a tGreenplumOutputBulk component. Used together they |
|
Log4j |
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html. |
For more information about tGreenplumBulkExec,
see: