The tMysqlOutputBulk and tMysqlBulkExec components are 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 statement used to feed a database. These two steps are fused together in the
tMysqlOutputBulkExec component, detailed in a
separate 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/Mysql |
|
Function |
Executes the Insert action on the data provided. |
|
Purpose |
As a dedicated component, tMysqlBulkExec offers gains in performance while |
|
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 My SQL that you are using. |
|
Use an existing connection |
Select this check box and in the Component List click the NoteWhen a Job contains the parent Job and the child Job, if you need to share an existing
For an example about how to share a database connection across Job levels, see |
|
Host |
Database server IP address |
|
Port |
Listening port number of DB server. |
|
Database |
Name of the database |
|
Username and |
DB user authentication data. To enter the password, click the […] button next to the |
|
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
Truncate table: The table content |
|
Table |
Name of the table to be written. Note that only one table can be |
|
Local file Name |
Name of the file to be loaded. This file should be located on the same machine where the Studio |
|
Schema and Edit |
A schema is a row description, it defines the number of fields to 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. |
Advanced settings |
Additional JDBC parameters |
Specify additional connection properties for the DB connection you |
|
Lines terminated by |
Character or sequence of characters used to separate lines. |
|
Fields terminated by |
Character, string or regular expression to separate fields. |
|
Enclosed by |
Character used to enclose text. |
|
Action on data |
On the data of the table defined, you can perform:
Insert records in table: Add new
Update records in table: Make
Replace records in table: Replace |
|
Records contain NULL value |
Check this box if you want to retrieve the null values from the |
|
Encoding |
Select the encoding from the list or select Custom and define it manually. This field is |
|
tStatCatcher Statistics |
Select this check box to collect log data at the component |
Dynamic settings |
Click the [+] button to add a row in the table and fill The Dynamic settings table is available only when the For more information on Dynamic settings and context |
|
Usage |
This component is to be used along with tMysqlOutputBulk component. Used together, they can |
|
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 |
Due to license incompatibility, one or more JARs required to use this component are not |
For use cases in relation with tMysqlBulkExec, see
the following scenarios: