tInformixOutputBulk and tInformixBulkExec 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 the
tInformixOutputBulkExec
component.
Component Family |
Databases/Informix |
|
Function |
tInformixOutputBulkExec carries |
|
Purpose |
tInformixOutputBulkExec is a |
|
Basic settings |
Property Type |
Either Built-in or Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
No properties stored centrally |
|
|
Repository: Select the repository |
|
Execution platform |
Select the operating system you are using. |
|
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 |
DB server listening port. |
|
Database |
Name of the database. |
|
Schema |
Name of the schema. |
|
Username and |
DB user authentication data. To enter the password, click the […] button next to the |
|
Instance |
Name of the Informix instance to be used. This information can |
|
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 |
|
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
|
||
|
Informix Directory |
Informix installation directory, e.g. ” |
|
Data file |
Name of the file to be generated and loaded. |
|
Append |
Select this check box to add rows to the end of the file. |
|
Action on data |
Select the operation you want to perform:
Bulk insert Bulk update The details asked will be different |
Advanced settings |
Additional JDBC parameters |
Specify additional connection properties for the DB connection you NoteYou can press Ctrl+Space to |
|
Row separator |
String (ex: ” |
|
Fields terminated by |
Character, string or regular expression used to separate the |
|
Set DBMONEY |
Select this check box to define the decimal separator used in the |
|
Set DBDATE |
Select the date format you want to apply. |
|
Rows Before Commit |
Enter the number of rows to be processed before the commit. |
|
Bad Rows Before Abort |
Enter the number of rows in error at which point the Job should |
|
Create directory if not exists |
This check box is selected by default. It creates a directory to |
|
Custom the flush buffer size |
Select this box in order to customize the memory size used to |
|
Encoding |
Select the encoding from the list or select Custom and define it manually. This field is |
|
tStatCatcher Statistics |
Select this check box to collect the log data at a component |
|
Output |
Where the output should go. |
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 when no particular transformation |
|
Limitation |
The database server/client must be installed on the same machine |
For a scenario in which tInformixOutputBulkExec might
be used, see: