tVerticaBulkExec

tVerticaBulkExec Properties

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,
detailed in a separate section. The advantage of using two separate components is that
the data can be transformed before it is loaded in the database.

Component family	Databases/Vertica
Function	Executes the Insert action on the data provided.
Purpose	As a dedicated component, tVerticaBulkExec offers gains in performance while carrying out the Insert operations to a Mysql database
Basic settings	Property type	Either Built-in or Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions.
		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.
	DB Version	Select the version of Vertica you are using from the list.
	Use an existing connection	Select this check box and in the Component List click the relevant connection component to reuse the connection details you already defined. Note 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: In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection. In the child level, use a dedicated connection component to read that registered database connection. 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	Name of the database schema you want to use.
	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.
	Action on table	On the table defined, you can perform one of the following operations: None: No operation is carried out. Drop and create table: The table is removed and created again. Create table: The table does not exist and gets created. Create table if not exists: The table is created if it does not exist. Drop table if exists and create: The table is removed if it already exists and created again. Clear table: The table content is deleted. You have the possibility to rollback the operation.
	Table	Name of the table to be written. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed.
	Schema and Edit Schema	A schema is a row description. It defines the number of fields to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions.
		Built-In: You create and store the schema locally for this component only. Related topic: see Talend Studio User Guide.
		Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs. Related topic: see Talend Studio User Guide. 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 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 current schema is of the Repository type, three options are available: View schema: choose this option to view the schema only. Change to built-in property: choose this option to change the schema to Built-in for local changes. Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the [Repository Content] window.
	File Name	Name of the file to be loaded. This file should be located on the same machine where the Studio is installed or where the Job using tVerticaBulkExec is deployed.
Advanced settings	Additional JDBC Parameters	Specify additional JDBC parameters for the database connection being created. This option is not available when the Use an existing connection check box in the Basic settings tab is selected.
	Action on data	On the data of the table defined, you can perform: Bulk insert: Add multiple entries to the table. If duplicates are found, the Job stops. Bulk update: Make simultaneous changes to multiple entries.
	Write to ROS (Read Optimized Store)	Select this check box to store the data in a physical storage area, in order to optimize the reading, as the data is compressed and pre-sorted.
	Exit job if no row was loaded	The Job automatically stops if no row has been loaded.
	Fields terminated by	Character, string or regular expression to separate fields.
	Null string	String displayed to indicate that the value is null.
	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 row to.
	tStatCatcher Statistics	Select this check box to collect log data at the component level.
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 more information on Dynamic settings and context variables, see Talend Studio User Guide.
Global Variables	ACCEPTED_ROW_NUMBER: the number of rows loaded into the database. REJECTED_ROW_NUMBER: the number of rows rejected. ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box. A Flow variable functions during the execution of a component while an After variable functions after the execution of the component. To fill up a field or expression with a variable, press Ctrl + Space to access the variable list and choose the variable to use from it. For further information about variables, see Talend Studio User Guide.
Usage	This component is to be used along with tVerticaOutputBulk component. Used together, they can offer gains in performance while feeding a Vertica database.
Log4j	The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide. 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	Due to license incompatibility, one or more JARs required to use this component are not provided. You can install the missing JARs for this particular component by clicking the Install button on the Component tab view. You can also find out and add all missing JARs easily on the Modules tab in the Integration perspective of your studio. For details, see https://help.talend.com/display/KB/How+to+install+external+modules+in+the+Talend+products or the section describing how to configure the Studio in the Talend Installation and Upgrade Guide.

Tips and Techniques

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.

Related scenarios

For related topics, see:

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 5.x

0 Comments

Inline Feedbacks

View all comments

tVerticaBulkExec – Docs for ESB 5.x