tGreenplumBulkExec Standard properties
These properties are used to configure tGreenplumBulkExec running in the Standard Job framework.
The Standard tGreenplumBulkExec component belongs to the Databases family.
The component in this framework is available in all Talend products.
Basic settings
Database |
Select a type of database from the list and click Apply. |
Property type |
Either Built-in or Repository . |
|
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. |
Use an existing connection |
Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined. Information noteNote: When a Job contains the parent Job and the child Job, if you
need to share an existing connection between the two levels, for example, to share the
connection created by the parent Job with the child Job, you have to:
For an example about how to share a database connection across Job levels, see Talend Studio User Guide. |
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 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 |
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 a table if exists and create: The table is removed if it already exists and created again. Clear a table: The table content is deleted. |
Filename |
Name of the file to be loaded. Information noteWarning:
This file is located on the machine specified by the URI in the Host field so it should be on the same machine as the database server. |
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. When you create a Spark Job, avoid the reserved word line when naming the fields. |
|
Built-In: You create and store the schema locally for this component only. |
|
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. For more information, see the related description of retrieving table schemas in Talend Studio User Guide. |
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
|
Advanced settings
Additional JDBC Parameters |
Specify additional JDBC parameters for the database connection created. Information noteNote: This field is available only when you have installed the 7.3.1-R2022-09 Studio Monthly update or a later one delivered by Talend. For more
information, check with your administrator.
|
DB driver |
Select the desired database driver from the drop-down list, which can be Greenplum and PostgreSQL and defaults to Greenplum. Note that the database driver for PostgreSQL is deprecated and will not be updated in R2021-01 Studio Monthly update and the coming releases. This option is available when Use an existing connection is not selected in the Basic settings view. Information noteNote: This option defaults to Greenplum when you have
installed the R2021-01 Studio Monthly update or a later one delivered by
Talend. For more information, check with your administrator.
|
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. |
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. |
tStat Catcher Statistics |
Select this check box to collect log data at the component level. |
Usage
Usage rule |
This component is generally used with a tGreenplumOutputBulk component. Used together they offer gains in performance while feeding a Greenplum database. |
Dynamic settings |
Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your database connection dynamically from multiple connections planned in your Job. This feature is useful when you need to access database tables having the same data structure but in different databases, especially when you are working in an environment where you cannot change your Job settings, for example, when your Job has to be deployed and executed independent of Talend Studio. The Dynamic settings table is available only when the Use an existing connection check box is selected in the Basic settings view. Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable. For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Talend Studio User Guide. |