tParAccelBulkExec
Improves performance when loading data in ParAccel
database.
The tParAccelOutputBulk and tParAccelBulkExec 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.
The tParAccelBulkExec performs an
Insert action on the data.
tParAccelBulkExec Standard properties
These properties are used to configure tParAccelBulkExec running in the Standard Job framework.
The Standard
tParAccelBulkExec component belongs to the Databases family.
The component in this framework is available in all Talend
products.
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.
Basic settings
Database |
Select a type of database from the list and click |
Property type |
Either Built-in or |
 |
Built-in: No property data stored |
 |
Repository: Select the repository |
Use an existing connection |
Select this check box and in the Component List click the relevant connection component to 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:
For an example about how to share a database connection |
Host |
Database server IP address. |
Port |
Listening port number of the DB server. |
Database |
Database name. |
Schema |
Exact name of the schema. |
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 |
 |
Built-In: You create and store the schema locally for this component |
 |
Repository: You have already created the schema and stored it in the When the schema to be reused has default values that are You can find more details about how to |
 |
Click Edit
|
Advanced settings
Additional JDBC Parameters |
Specify additional JDBC parameters for the This property is not available when the Use an existing connection |
Copy mode |
Select the copy mode you want to use from either:
Basic: Standard mode, without
Parallel: Allows you to use several |
Filename |
Name of the file to be loaded. Warning:
This file is located on the machine specified by the URI in |
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 |
Remove Quotes |
Select this check box to remove quotation marks from the file to |
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 |
Log file |
Browse to or enter the access path to the log file in your |
Logging level |
Select the information type you want to record in your log |
tStat |
Select this check box to collect log data at the component |
Usage
Usage rule |
This component covers all possible SQL database queries. It allows |
Dynamic settings |
Click the [+] button to add a row in the table The Dynamic settings table is For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic |
Limitation |
Due to license incompatibility, one or more JARs required to use |
Related scenarios
For related scenarios, see:
-
Inserting transformed data in MySQL database of tMysqlOutputBulk.
-
Inserting data in bulk in MySQL database of tMysqlOutputBulkExec.
-
Truncating and inserting file data into an Oracle database of tOracleBulkExec.