tJDBCOutput - 6.3

Talend Components Reference Guide

EnrichVersion
6.3
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
task
Data Governance
Data Quality and Preparation
Design and Development
EnrichPlatform
Talend Studio

Function

tJDBCOutput writes, updates, makes changes or suppresses entries in any type of database connected to a JDBC API.

Purpose

tJDBCOutput executes the action defined on the data contained in the table, based on the flow incoming from the preceding component in the Job.

Depending on the Talend solution you are using, this component can be used in one, some or all of the following Job frameworks:

  • Standard: see tJDBCOutput properties.

    The component in this framework is generally available.

  • MapReduce: see tJDBCOutput in Talend Map/Reduce Jobs.

    The component in this framework is available only if you have subscribed to one of the Talend solutions with Big Data.

  • Spark Batch: see tJDBCOutput in Spark Batch Jobs.

    This component can be used to write data to a RDS MariaDB, a RDS PostgreSQL or a RDS SQLServer database.

    The component in this framework is available only if you have subscribed to one of the Talend solutions with Big Data.

  • Spark Streaming: see tJDBCOutput in Spark Streaming Jobs.

    This component can be used to write data to a RDS MariaDB, a RDS PostgreSQL or a RDS SQLServer database.

    The component in this framework is available only if you have subscribed to Talend Real-time Big Data Platform or Talend Data Fabric.

tJDBCOutput properties

Component family

Databases/JDBC

 

Basic settings

Property type

Either Built-In or Repository.

 

 

Built-In: No property data stored centrally.

 

 

Repository: Select the repository file where the properties are stored.

 

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:

  1. 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.

  2. 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.

 

Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

For more information about setting up and storing database connection parameters, see Talend Studio User Guide.

 

JDBC URL

Type in the database location path. For example, if a MySQL database called Talend is hosted by a machine located at an IP address XX.XX.XX.XX and the port is 3306, then the URL should be jdbc:mysql://XX.XX.XX.XX:3306/Talend.

 

Driver JAR

Click the plus button under the table to add lines of the count of your need for the purpose of loading several JARs. Then on each line, click the three dot button to open the Select Module wizard from which you can select a driver JAR of your interest for each line.

 

Class Name

Type in the Class name to be pointed to in the driver. For example, for the mysql-connector-java-5.1.2.jar driver, the name to be entered is org.gjt.mm.mysql.Driver.

 

Username and Password

Enter the authentication information to the database you need to connect to.

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 data

On the data of the table defined, you can perform:

Insert: Add new entries to the table. If duplicates are found, Job stops.

Update: Make changes to existing entries

Insert or update: Insert a new record. If the record with the given reference already exists, an update would be made.

Update or insert: Update the record with the given reference. If the record does not exist, a new record would be inserted.

Delete: Remove entries corresponding to the input flow.

Warning

It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). For an advanced use, click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. To do that: Select the Use field options check box and then in the Key in update column, select the check boxes next to the column names you want to use as a base for the Update operation. Do the same in the Key in delete column for the Delete operation.

 

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

 

 

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 the article Verifying default values in a retrieved schema on Talend Help Center (https://help.talend.com).

  

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.

 

Die on error

Select this check box to stop the execution of the Job when an error occurs.

Clear the check box to skip any rows on error and complete the process for error-free rows. When errors are skipped, you can collect the rows on error using a Row > Reject link.

 

Specify a data source alias

Select this check box and specify the alias of a data source created on the Talend Runtime side to use the shared connection pool defined in the data source configuration. This option works only when you deploy and run your Job in Talend Runtime. For a related use case, see Scenario 4: Retrieving data from a MySQL database using the data source on Talend Runtime side to set up the database connection.

Warning

If you use the component's own DB configuration, your data source connection will be closed at the end of the component. To prevent this from happening, use a shared DB connection with the data source alias specified.

This check box is not available when the Use an existing connection check box is selected.

Advanced settings

Commit every

Enter the number of rows to be completed before committing batches of rows together into the database. This option ensures transaction quality (but not rollback) and, above all, better performance at execution.

 

Additional Columns

This option is not offered if you create (with or without drop) the database table. This option allows you to call SQL functions to perform actions on columns, which are not insert, nor update or delete actions, or action that require particular preprocessing.

 

 

Name: Type in the name of the schema column to be altered or inserted as new column

 

 

SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data.

 

 

Position: Select Before, Replace or After following the action to be performed on the reference column.

 

 

Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column.

 

Use field options

Select this check box to customize a request, especially when there is double action on data.

 

Enable debug mode

Select this check box to display each step during processing entries in a database.

 

Use Batch

Select this check box to activate the batch mode for data processing.

 

Batch Size

Specify the number of records to be processed in each batch..

This field appears only when the Use batch mode check box is selected.

 

tStat Catcher Statistics

Select this check box to collect 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, see Talend Studio User Guide.

Note that when parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subjob.

Warning

  • 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.

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 examples on using dynamic parameters, see Scenario 3: Reading data from MySQL databases through context-based dynamic connections and Scenario: Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Talend Studio User Guide.

Global Variables 

NB_LINE: the number of rows processed. This is an After variable and it returns an integer.

NB_LINE_UPDATED: the number of rows updated. This is an After variable and it returns an integer.

NB_LINE_INSERTED: the number of rows inserted. This is an After variable and it returns an integer.

NB_LINE_DELETED: the number of rows deleted. This is an After variable and it returns an integer.

NB_LINE_REJECTED: the number of rows rejected. This is an After variable and it returns an integer.

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 offers the flexibility benefit of the database query and covers all of the SQL queries possible.

This component must be used as an output component. It allows you to carry out actions on a table or on the data of a table in a JDBC database. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. For an example of tMySqlOutput in use, see Scenario 3: Retrieve data in error with a Reject link.

Log4j

If you are using a subscription-based version of the Studio, 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.

tJDBCOutput in Talend Map/Reduce Jobs

Warning

The information in this section is only for users that have subscribed to one of the Talend solutions with Big Data and is not applicable to Talend Open Studio for Big Data users.

In a Talend Map/Reduce Job, tJDBCOutput, as well as the other Map/Reduce components preceding it, generates native Map/Reduce code. This section presents the specific properties of tJDBCOutput when it is used in that situation. For further information about a Talend Map/Reduce Job, see Talend Big Data Getting Started Guide.

Component family

MapReduce/Output

 

Basic settings

Property type

Either Built-In or Repository.

 

 

Built-In: No property data stored centrally.

 

 

Repository: Select the repository file where the properties are stored.

 

Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

For more information about setting up and storing database connection parameters, see Talend Studio User Guide.

 

JDBC URL

Type in the database location path. For example, if a MySQL database called Talend is hosted by a machine located at an IP address XX.XX.XX.XX and the port is 3306, then the URL should be jdbc:mysql://XX.XX.XX.XX:3306/Talend.

 

Driver JAR

Click the plus button under the table to add lines of the count of your need for the purpose of loading several JARs. Then on each line, click the three dot button to open the Select Module wizard from which you can select a driver JAR of your interest for each line.

 

Class Name

Type in the Class name to be pointed to in the driver. For example, for the mysql-connector-java-5.1.2.jar driver, the name to be entered is org.gjt.mm.mysql.Driver.

 

Username and Password

Enter the authentication information to the database you need to connect to.

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

Name of the table to be written. Note that only one table can be written at a time.

 

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

  

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.

Advanced settings

Use Batch Size

When selected, enables you to define the number of lines in each processed batch.

Usage in Map/Reduce Jobs

In a Talend Map/Reduce Job, it is used as an end component and requires a transformation component as input link. The other components used along with it must be Map/Reduce components, too. They generate native Map/Reduce code that can be executed directly in Hadoop.

This component, along with the MapReduce family it belongs to, appears only when you are creating a Map/Reduce Job.

Note that in this documentation, unless otherwise explicitly stated, a scenario presents only Standard Jobs, that is to say traditional Talend data integration Jobs, and non Map/Reduce Jobs.

Hadoop Connection

You need to use the Hadoop Configuration tab in the Run view to define the connection to a given Hadoop distribution for the whole Job.

This connection is effective on a per-Job basis.

Limitation

We recommend using the following databases with the Map/Reduce version of this component: DB2, Informix, MSSQL, MySQL, Netezza, Oracle, Postgres, Teradata and Vertica.

It may work with other databases as well, but these may not necessarily have been tested.

Related scenarios

If you are a subscription-based Big Data user, you can consult a Talend Map/Reduce Job using the Map/Reduce version of tJDBCOutput:

tJDBCOutput in Spark Batch Jobs

Component family

Databases/DB JDBC

 

Basic settings

Property type

Either Built-In or Repository.

 

 

Built-In: No property data stored centrally.

 

 

Repository: Select the repository file where the properties are stored.

 

Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

For more information about setting up and storing database connection parameters, see Talend Studio User Guide.

 

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.

 

JDBC URL

Type in the database location path. For example, if a MySQL database called Talend is hosted by a machine located at an IP address XX.XX.XX.XX and the port is 3306, then the URL should be jdbc:mysql://XX.XX.XX.XX:3306/Talend.

If you are using Spark V1.3, this URL should contain the authentication information, such as:

jdbc:mysql://XX.XX.XX.XX:3306/Talend?user=ychen&password=talend

 

Driver JAR

Click the plus button under the table to add lines of the count of your need for the purpose of loading several JARs. Then on each line, click the three dot button to open the Select Module wizard from which you can select a driver JAR of your interest for each line.

 

Class Name

Type in the Class name to be pointed to in the driver. For example, for the mysql-connector-java-5.1.2.jar driver, the name to be entered is org.gjt.mm.mysql.Driver.

 

Username and Password

Enter the authentication information to the database you need to connect to.

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.

Available only for Spark V1.4. and onwards.

 

Table name

Name of the table to be written. Note that only one table can be written at a time.

 

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

  

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.

 

Action on data

On the data of the table defined, you can perform one of the following operations:

  • Insert: Add new entries to the table.

  • Update: Make changes to existing entries.

  • Insert or update: Insert a new record. If the record with the given reference already exists, an update would be made.

  • Update or insert: Update the record with the given reference. If the record does not exist in the index pool, a new record would be inserted.

  • Delete: Remove entries corresponding to the input flow.

 

Die on error

Select this check box to stop the execution of the Job when an error occurs.

Advanced settings

Additional JDBC parameters

Specify additional connection properties for the database connection you are creating. The properties are separated by semicolon and each property is a key-value pair, for example, encryption=1;clientname=Talend.

This field is not available if the Use an existing connection check box is selected.

 

Left protected char and Right protected char

Enter the symbol reserved by the database you are using, the left part in Left protected char and the right part in Right protected char, so that tJDBCOutput can generate SQL expressions with this reserved symbol properly placed.

For example, if you are using Oracle, double quotation marks (") are reserved for object names and so you need to enter the left and the right marks in these fields, respectively. Then at runtime, tJDBCOutput places double quotations marks around object names such as a table name.

 

Additional Columns

This option allows you to call SQL functions to perform actions on columns, provided that these are not insert, update or delete actions, or actions that require pre-processing. This option is not available if you have just created the database table (even if you delete it beforehand). Click the [+] button under the table to add column(s), and set the following parameters for each column.

 

 

Name: Type in the name of the schema column to be altered or inserted.

 

 

SQL expression: Type in the SQL statement to be executed in order to alter or insert the data in the corrsponding column.

 

 

Position: Select Before, Replace or After, depending on the action to be performed on the reference column.

 

 

Reference column: Type in a reference column that the current component can use to locate or replace the new column, or the column to be modified.

 

Use field options

Select the check box for the corresponding column to customize a request, particularly if multiple actions are being carried out on the data.

  • Key in update: Select the check box for the corresponding column based on which the data is updated.

  • Key in delete: Select the check box for the corresponding column based on which the data is deleted.

  • Updatable: Select the check box if the data in the corresponding column can be updated.

  • Insertable: Select the check box if the data in the corresponding column can be inserted.

 

Use Batch

Select this check box to activate the batch mode for data processing.

This check box is available only when the Insert, the Update or the Delete option is selected from the Action on data list in the Basic settings view.

 

Batch Size

Specify the number of records to be processed in each batch..

This field appears only when the Use batch mode check box is selected.

 

Connection pool

In this area, you configure, for each Spark executor, the connection pool used to control the number of connections that stay open simultaneously. The default values given to the following connection pool parameters are good enough for most use cases.

  • Max total number of connections: enter the maximum number of connections (idle or active) that are allowed to stay open simultaneously.

    The default number is 8. If you enter -1, you allow unlimited number of open connections at the same time.

  • Max waiting time (ms): enter the maximum amount of time at the end of which the response to a demand for using a connection should be returned by the connection pool. By default, it is -1, that is to say, infinite.

  • Min number of idle connections: enter the minimum number of idle connections (connections not used) maintained in the connection pool.

  • Max number of idle connections: enter the maximum number of idle connections (connections not used) maintained in the connection pool.

 

Evict connections

Select this check box to define criteria to destroy connections in the connection pool. The following fields are displayed once you have selected it.

  • Time between two eviction runs: enter the time interval (in milliseconds) at the end of which the component checks the status of the connections and destroys the idle ones.

  • Min idle time for a connection to be eligible to eviction: enter the time interval (in milliseconds) at the end of which the idle connections are destroyed.

  • Soft min idle time for a connection to be eligible to eviction: this parameter works the same way as Min idle time for a connection to be eligible to eviction but it keeps the minimum number of idle connections, the number you define in the Min number of idle connections field.

Usage in Spark Batch Jobs

This component is used as an end component and requires an input link.

This component should use a tJDBCConfiguration component present in the same Job to connect to a database. You need to drop a tJDBCConfiguration component alongside this component and configure the Basic settings of this component to use tJDBCConfiguration.

This component, along with the Spark Batch component Palette it belongs to, appears only when you are creating a Spark Batch Job.

Note that in this documentation, unless otherwise explicitly stated, a scenario presents only Standard Jobs, that is to say traditional Talend data integration Jobs.

Log4j

If you are using a subscription-based version of the Studio, 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.

Spark Connection

You need to use the Spark Configuration tab in the Run view to define the connection to a given Spark cluster for the whole Job. In addition, since the Job expects its dependent jar files for execution, one and only one file system related component from the Storage family is required in the same Job so that Spark can use this component to connect to the file system to which the jar files dependent on the Job are transferred:

This connection is effective on a per-Job basis.

Related scenarios

For a scenario about how to use the same type of component in a Spark Batch Job, see Writing and reading data from MongoDB using a Spark Batch Job.

tJDBCOutput in Spark Streaming Jobs

Component family

Databases/DB JDBC

 

Basic settings

Property type

Either Built-In or Repository.

 

 

Built-In: No property data stored centrally.

 

 

Repository: Select the repository file where the properties are stored.

 

Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

For more information about setting up and storing database connection parameters, see Talend Studio User Guide.

 

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.

 

JDBC URL

Type in the database location path. For example, if a MySQL database called Talend is hosted by a machine located at an IP address XX.XX.XX.XX and the port is 3306, then the URL should be jdbc:mysql://XX.XX.XX.XX:3306/Talend.

If you are using Spark V1.3, this URL should contain the authentication information, such as:

jdbc:mysql://XX.XX.XX.XX:3306/Talend?user=ychen&password=talend

 

Driver JAR

Click the plus button under the table to add lines of the count of your need for the purpose of loading several JARs. Then on each line, click the three dot button to open the Select Module wizard from which you can select a driver JAR of your interest for each line.

 

Class Name

Type in the Class name to be pointed to in the driver. For example, for the mysql-connector-java-5.1.2.jar driver, the name to be entered is org.gjt.mm.mysql.Driver.

 

Username and Password

Enter the authentication information to the database you need to connect to.

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.

Available only for Spark V1.4. and onwards.

 

Table

Name of the table to be written. Note that only one table can be written at a time.

 

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

  

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.

 

Action on data

On the data of the table defined, you can perform one of the following operations:

  • Insert: Add new entries to the table.

  • Update: Make changes to existing entries.

  • Insert or update: Insert a new record. If the record with the given reference already exists, an update would be made.

  • Update or insert: Update the record with the given reference. If the record does not exist in the index pool, a new record would be inserted.

  • Delete: Remove entries corresponding to the input flow.

 

Die on error

Select this check box to stop the execution of the Job when an error occurs.

Advanced settings

Additional JDBC parameters

Specify additional connection properties for the database connection you are creating. The properties are separated by semicolon and each property is a key-value pair, for example, encryption=1;clientname=Talend.

This field is not available if the Use an existing connection check box is selected.

Advanced settings

Left protected char and Right protected char

Enter the symbol reserved by the database you are using, the left part in Left protected char and the right part in Right protected char, so that tJDBCOutput can generate SQL expressions with this reserved symbol properly placed.

For example, if you are using Oracle, double quotation marks (") are reserved for object names and so you need to enter the left and the right marks in these fields, respectively. Then at runtime, tJDBCOutput places double quotations marks around object names such as a table name.

 

Additional Columns

This option allows you to call SQL functions to perform actions on columns, provided that these are not insert, update or delete actions, or actions that require pre-processing. This option is not available if you have just created the database table (even if you delete it beforehand). Click the [+] button under the table to add column(s), and set the following parameters for each column.

 

 

Name: Type in the name of the schema column to be altered or inserted.

 

 

SQL expression: Type in the SQL statement to be executed in order to alter or insert the data in the corrsponding column.

 

 

Position: Select Before, Replace or After, depending on the action to be performed on the reference column.

 

 

Reference column: Type in a reference column that the current component can use to locate or replace the new column, or the column to be modified.

 

Use field options

Select the check box for the corresponding column to customize a request, particularly if multiple actions are being carried out on the data.

  • Key in update: Select the check box for the corresponding column based on which the data is updated.

  • Key in delete: Select the check box for the corresponding column based on which the data is deleted.

  • Updatable: Select the check box if the data in the corresponding column can be updated.

  • Insertable: Select the check box if the data in the corresponding column can be inserted.

 

Use Batch

Select this check box to activate the batch mode for data processing.

This check box is available only when the Insert, the Update or the Delete option is selected from the Action on data list in the Basic settings view.

 

Batch Size

Specify the number of records to be processed in each batch..

This field appears only when the Use batch mode check box is selected.

 

Connection pool

In this area, you configure, for each Spark executor, the connection pool used to control the number of connections that stay open simultaneously. The default values given to the following connection pool parameters are good enough for most use cases.

  • Max total number of connections: enter the maximum number of connections (idle or active) that are allowed to stay open simultaneously.

    The default number is 8. If you enter -1, you allow unlimited number of open connections at the same time.

  • Max waiting time (ms): enter the maximum amount of time at the end of which the response to a demand for using a connection should be returned by the connection pool. By default, it is -1, that is to say, infinite.

  • Min number of idle connections: enter the minimum number of idle connections (connections not used) maintained in the connection pool.

  • Max number of idle connections: enter the maximum number of idle connections (connections not used) maintained in the connection pool.

 

Evict connections

Select this check box to define criteria to destroy connections in the connection pool. The following fields are displayed once you have selected it.

  • Time between two eviction runs: enter the time interval (in milliseconds) at the end of which the component checks the status of the connections and destroys the idle ones.

  • Min idle time for a connection to be eligible to eviction: enter the time interval (in milliseconds) at the end of which the idle connections are destroyed.

  • Soft min idle time for a connection to be eligible to eviction: this parameter works the same way as Min idle time for a connection to be eligible to eviction but it keeps the minimum number of idle connections, the number you define in the Min number of idle connections field.

Usage in Spark Streaming Jobs

This component is used as an end component and requires an input link.

This component should use a tJDBCConfiguration component present in the same Job to connect to a database. You need to drop a tJDBCConfiguration component alongside this component and configure the Basic settings of this component to use tJDBCConfiguration.

This component, along with the Spark Streaming component Palette it belongs to, appears only when you are creating a Spark Streaming Job.

Note that in this documentation, unless otherwise explicitly stated, a scenario presents only Standard Jobs, that is to say traditional Talend data integration Jobs.

Log4j

If you are using a subscription-based version of the Studio, 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.

Spark Connection

You need to use the Spark Configuration tab in the Run view to define the connection to a given Spark cluster for the whole Job. In addition, since the Job expects its dependent jar files for execution, one and only one file system related component from the Storage family is required in the same Job so that Spark can use this component to connect to the file system to which the jar files dependent on the Job are transferred:

This connection is effective on a per-Job basis.

Related scenarios

For a scenario about how to use the same type of component in a Spark Streaming Job, see Reading and writing data in MongoDB using a Spark Streaming Job.

tJDBCOutput in Talend Storm Jobs

Warning

The information in this section is only for users that have subscribed to one of the Talend solutions with Big Data and is not applicable to Talend Open Studio for Big Data users.

In a Talend Storm Job, tJDBCOutput, as well as the other Storm components preceding it, generates native Storm code to build the Storm topology to be seamlessly used in your Storm ecosystem. This section presents the specific properties of tJDBCOutput when it is used in that situation. For further information about a Talend Storm Job, see Talend Big Data Getting Started Guide.

Component family

Storm/Output

 

Basic settings

Property type

Either Built-In or Repository.

 

 

Built-In: No property data stored centrally.

 

 

Repository: Select the repository file where the properties are stored.

 

Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

For more information about setting up and storing database connection parameters, see Talend Studio User Guide.

 

JDBC URL

Type in the database location path. For example, if a MySQL database called Talend is hosted by a machine located at an IP address XX.XX.XX.XX and the port is 3306, then the URL should be jdbc:mysql://XX.XX.XX.XX:3306/Talend.

 

Driver JAR

Click the plus button under the table to add lines of the count of your need for the purpose of loading several JARs. Then on each line, click the three dot button to open the Select Module wizard from which you can select a driver JAR of your interest for each line.

 

Class Name

Type in the Class name to be pointed to in the driver. For example, for the mysql-connector-java-5.1.2.jar driver, the name to be entered is org.gjt.mm.mysql.Driver.

 

Username and Password

Type in the database location path. For example, if a MySQL database called Talend is hosted by a machine located at an IP address XX.XX.XX.XX and the port is 3306, then the URL should be jdbc:mysql://XX.XX.XX.XX:3306/Talend.

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

Name of the table to be written. Note that only one table can be written at a time.

 

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

  

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.

Usage in Storm Jobs

In a Talend Storm Job, it is used as an end component. The other components used along with it must be Storm components, too. They generate native Storm code that can be executed directly in a Storm system.

This component, along with the Storm family it belongs to, appears only when you are creating a Storm Job.

Note that in this documentation, unless otherwise explicitly stated, a scenario presents only Standard Jobs, that is to say traditional Talend data integration Jobs.

Storm Connection

You need to use the Storm Configuration tab in the Run view to define the connection to a given Storm system for the whole Job.

This connection is effective on a per-Job basis.

Limitation

n/a

Related scenarios

No scenario is available for the Storm version of this component yet.