tIngresOutputBulk and tIngresBulkExec 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
tIngresOutputBulkExec component, detailed in
another section. The advantage of using two components is that data can be transformed
before it is loaded in the database.
Component family |
Databases/Ingres |
|
Function |
Executes the Insert action on the data provided. |
|
Purpose |
Inserts data in bulk to a table in the Ingres DBMS for performance |
|
Basic settings |
Property type |
Either Built-in or Repository. Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-in: No property data stored |
|
|
Repository: Select the repository |
|
Table |
Name of the table to be filled. |
|
VNode |
Name of the virtual node. |
|
Database |
Name of the database. |
|
Action on table |
Actions that can be taken on the table defined:
None: No operation made to the
Truncate: Delete all the rows in |
File name |
Name of the file to be loaded. WarningThis file should be located on the same machine as the |
|
|
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
|
||
|
Delete Working Files After Use |
Select this check box to delete the files that are created during |
Advanced settings |
Field Separator |
Character, string or regular expression to separate fields. |
Row Separator |
String (ex: ” |
|
Null Indicator |
Value of the null indicator. |
|
Session User |
User of the defined session (the connection to the |
|
Rollback |
Enable or disable rollback. |
|
On Error |
Policy of error handling:
Continue: Continue the
Terminate: Terminate the |
|
Reject Row File |
Path and name of the file that holds the rejected rows. Available when Continue is |
|
Error Count |
Number of errors to trigger the termination of the Available when Terminate is |
|
Allocation |
Number of pages initially allocated to the table or index. |
|
Extend |
Number of pages by which a table or index grows. |
|
Fill Factor |
Specify the percentage (from 1 to 100) of each primary data page |
|
Min Pages/Max |
Specify the minimum/maximum number of primary pages a hash table |
|
|
Leaf Fill |
A bulk copy from can specify a leaffill value. This clause |
|
Non Leaf Fill |
A bulk copy from can specify a nonleaffill value. This clause |
Row Estimate |
Specify the estimated number of rows to be copied from a file to a |
|
Trailing WhiteSpace |
Selected by default, this check box is designed to trim the |
|
Encoding |
List of the encoding schemes. |
|
Output |
Where to output the error message: to console: Message output to the to global variable: Message |
|
|
tStatCatcher Statistics |
Select this check box to collect log data at the component |
Global Variables |
NB_LINE_DATA: the number of rows read. This is an After NB_LINE_BAD: the number of rows rejected. This is an ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see Talend Studio |
|
Usage |
Deployed along with tIngresOutputBulk, tIngresBulkExec feeds the given data in bulk to the |
|
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. |
|
Limitation |
The database server/client must be installed on the same machine Due to license incompatibility, one or more JARs required to use this component are not |