tParAccelBulkExec

tParAccelBulkExec Properties

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

Component Family	Databases/ParAccel
Function	tParAccelBulkExec performs an Insert action on the data.
Purpose	tParAccelBulkExec is a component which is specifically designed to improve performance when loading data in ParAccel 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.
	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 the DB server.
	Database	Database name.
	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 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 already exists and created again. Clear table: The table content is deleted.
	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.
Advanced settings	Copy mode	Select the copy mode you want to use from either: Basic: Standard mode, without optimisation. Parallel: Allows you to use several internal ParAccel APIs in order to optimise loading speed.
	Filename	Name of the file to be loaded. Warning 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.
	File Type	Select the file type from the list.
	Field Layout	Select the field layout from the list.
	Field separator	Character, string or regular expression to separate fields.
	Explicit IDs	The ID is already present in the file to be loaded or will be set by the database.
	Remove Quotes	Select this check box to remove quotation marks from the file to be loaded.
	Max. Errors	Type in the maximum number of errors before your Job stops.
	Date Format	Type in the date format to be used.
	Time/Timestamp Format	Enter the date and hour format to be used.
	Additional COPY Options	Enter the specific, customized ParAccel option that you want to use.
	Log file	Browse to or enter the access path to the log file in your directory.
	Logging level	Select the information type you want to record in your log file.
	tStat Catcher 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.
Usage	This component covers all possible SQL database queries. It allows you to carry out actions on a table or on the data of a table in a ParAccel database. It enables you to create a reject flow, with a Row > Reject link filtering the data in error. For a usage example, see Scenario 3: Retrieve data in error with a Reject link.
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.

Related scenarios

For a related scenario, see:

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

Thank you for watching.

Docs 5.x

0 Comments

Inline Feedbacks

View all comments

tParAccelBulkExec – Docs for ESB 5.x