Skip to main content Skip to complementary content

tMysqlOutputBulkExec Standard properties

These properties are used to configure tMysqlOutputBulkExec running in the Standard Job framework.

The Standard tMysqlOutputBulkExec component belongs to the Databases family.

The component in this framework is available in all Talend products.

Information noteNote: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see DB Generic components.

Basic settings

Database

Select the desired database type from the list and click Apply.

Property type

Either Built-in or Repository .

 

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 the database that you are using.

Host

Database server IP address

Port

Listening port number of DB server.

Database

Name of the database

Username and Password

DB user authentication data.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, 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 already 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.

Table

Name of the table to be written.

Information noteNote:

Note that only one table can be written at a time and that the table must already exist for the insert operation to succeed

Local FileName

Name of the file to be generated and loaded.

This file is generated on the same machine where Talend Studio is installed or where the Job using tMysqlOutputBulkExec is deployed. Then it is loaded to the database specified by Host field.

Append

Select the check box for this option to append new rows to the end of the file.

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.

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.

 

Built-In: You create and store the schema locally for this component only.

 

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

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 information, see Retrieving table schemas.

Advanced settings

Additional JDBC parameters

Specify additional connection properties for the DB connection you are creating. This option is not available if you have selected the Use an existing connection check box in the Basic settings.

Information noteNote:

You can press Ctrl+Space to access a list of predefined global variables.

Row separator

String (ex: "\n"on Unix) to distinguish rows.

Field separator

Character, string or regular expression to separate fields.

Escape char

Character of the row to be escaped

Text enclosure

Character used to enclose the text.

Create directory if does not exist

This check box is selected by default. It creates a directory to hold the output table if required.

Custom the flush buffer size

Customize the amount of memory used to temporarily store output data. In the Row number field, enter the number of rows after which the memory is to be freed again.

Action on data

On the data of the table defined, you can carry out the following opertaions:

Insert records in table: Add new records to the table.

Update records in table: Make changes to existing records.

Replace records in table: Replace existing records with new one. Ignore records in table: Ignore existing records or insert the new ones.

Records contain NULL value

This check box is selected by default. It allows you to take account of NULL value fields. If you clear the check box, the NULL values will automatically be replaced with empty values.

Encoding

Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling.

tStatCatcher Statistics

Select this check box to collect the log data at the component level.

Enable parallel execution

Select this check box to perform high-speed data processing, by treating multiple data flows simultaneously. Note that this feature depends on the database or the application ability to handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either:
  • Enter the number of parallel executions desired.
  • Press Ctrl + Space and select the appropriate context variable from the list. For further information about context variables, see Using contexts and variables.
  • The Action on table field is not available with the parallelization function. Therefore, you must use a tCreateTable component if you want to create a table.
  • When parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subJob.

Usage

Usage rule

This component is mainly used when no particular transformation is required on the data to be loaded onto the database.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!