The tVerticaOutputBulk and tVerticaBulkExec components are generally used together as parts of 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 tVerticaOutputBulkExec
component.
Component family |
Databases/Vertica |
|
Function |
tVerticaOutputBulkExec executes |
|
Purpose |
As a dedicated component, it allows gains in performance during |
|
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 |
|
DB Version |
Select the version of Vertica you are using from the list. |
Use existing connection |
Select this check box and in the Component List click the |
|
|
Host |
Database server IP address. |
|
Port |
Listening port number of DB server. |
|
DB Name |
Name of the database |
|
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 table: The table is
Create table: The table does not
Create table if not exists: The
Drop table if exists and create:
Clear 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 Click Edit schema to make changes to the schema. If the
|
|
|
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. |
|
File Name |
Name of the file to be generated and loaded. This file is generated on the same machine where the Studio is |
|
Append |
Select this check box to add the new rows at the end of the |
Advanced settings |
Additional JDBC Parameters |
Specify additional JDBC parameters for the database connection This option is not available when the Use an |
Write to ROS (Read Optimized Store) |
Select this check box to store the data in a physical storage |
|
|
Exit job if no row was loaded |
The Job automatically stops if no row has been loaded. |
|
Field Separator |
Character, string or regular expression to separate fields. |
|
Null string |
String displayed to indicate that the value is null. |
|
Include header |
Select this check box to include the column header to the file. |
|
Encoding |
Select the encoding from the list or select Custom and define it manually. This field is |
|
Rejected data file |
Specify a file you want to write rejected rows to. |
|
Exception log file |
Specify a file you want to write an explanation for each rejected |
|
tStatCatcher Statistics |
Select this check box to collect log data at the component |
Global Variables |
ACCEPTED_ROW_NUMBER: the number of rows loaded into the REJECTED_ROW_NUMBER: the number of rows rejected. 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 |
This component is mainly used when no particular transformation is |
|
Limitation |
Due to license incompatibility, one or more JARs required to use this component are not |
Used together, Talend Studio and the Vertica
database create very fast and affordable data warehouse and data mart applications. For more
information about how to configure Talend Studio to connect to
Vertica, see Talend and HP Vertica Tips and Techniques.
For use cases in relation with tVerticaOutputBulkExec, see the following scenarios: