tJDBCInput properties for Apache Spark Batch - Cloud - 8.0


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 ESB
Talend Real-Time Big Data Platform
Talend Studio
Data Governance > Third-party systems > Database components (Integration) > JDBC components
Data Quality and Preparation > Third-party systems > Database components (Integration) > JDBC components
Design and Development > Third-party systems > Database components (Integration) > JDBC components

These properties are used to configure tJDBCInput running in the Spark Batch Job framework.

The Spark Batch tJDBCInput component belongs to the Databases family.

This component also allows you to connect and read data from a RDS MariaDB, a RDS PostgreSQL or a RDS SQLServer database.

The component in this framework is available in all subscription-based Talend products with Big Data and Talend Data Fabric.

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 drop-down list, select the desired connection component to reuse the connection details you already defined.


The JDBC URL of the database to be used. For example, the JDBC URL for the Amazon Redshift database is jdbc:redshift://endpoint:port/database.

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

Driver JAR

Complete this table to load the driver JARs needed. To do this, click the [+] button under the table to add as many rows as needed, each row for a driver JAR, then select the cell and click the [...] button at the right side of the cell to open the Module dialog box from which you can select the driver JAR to be used. For example, the driver jar RedshiftJDBC41- for the Redshift database.

For more information, see Importing a database driver.

Class Name

Enter the class name for the specified driver between double quotation marks. For example, for the RedshiftJDBC41- driver, the name to be entered is

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, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Available only for Spark V1.4. and onwards.

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. When you create a Spark Job, avoid the reserved word line when naming the fields.

This component offers the advantage of the dynamic schema feature. This allows you to retrieve unknown columns from source files or to copy batches of columns from a source without mapping each column individually. For further information about dynamic schemas, see Talend Studio User Guide.

This dynamic schema feature is designed for the purpose of retrieving unknown columns of a table and is recommended to be used for this purpose only; it is not recommended for the use of creating tables.


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.


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.

Table Name

Type in the name of the table from which you need to read data.

This field is only available when you select Table from the Read from drop-down list.

Read from

Select the type of the source of the data to be read.
  • Table: tJDBCInput reads the data of the table you specify in the Table name field.

  • Query: tJDBCInput reads the result of the query you write in the Query field.

Query type and Query

Specify the database query statement paying particularly attention to the properly sequence of the fields which must correspond to the schema definition.

If you are using Spark V2.0 onwards, the Spark SQL does not recognize the prefix of a database table anymore. This means that you must enter only the table name without adding any prefix that indicates for example the schema this table belongs to.

For example, if you need to perform a query in a table system.mytable, in which the system prefix indicates the schema that the mytable table belongs to, in the query, you must enter mytable only.

You can use pushdown predicate in the query to filter the data from the database. Spark supports the following operators:
  • Filter
  • Limit

These fields are only available when you select Query from the Read from drop-down list.

Guess Query

Click the Guess Query button to generate the query which corresponds to your table schema in the Query field.

Guess schema

Click the Guess schema button to retrieve the table schema.

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.

Spark SQL JDBC parameters

Add the JDBC properties supported by Spark SQL to this table. For a list of the user configurable properties, see JDBC to other database.

This component automatically set the url, dbtable and driver properties by using the configuration from the Basic settings tab.

Trim all the String/Char columns

Select this check box to remove leading whitespace and trailing whitespace from all String/Char columns.

Trim column

This table is filled automatically with the schema being used. Select the check box(es) corresponding to the column(s) to be trimmed.

Enable partitioning

Select this check box to read data in partitions.

Define, within double quotation marks, the following parameters to configure the partitioning:
  • Partition column: the numeric column used as partition key.

  • Lower bound of the partition stride and Upper bound of the partition stride: enter the upper bounds and the lower bound to determine the partition stride. These bounds do not filter the table rows. All rows in the table are partitioned and returned.

  • Number of partitions: the number of partitions into which the table rows are split. Each Spark worker handles only one of the partitions at a time.

The average size of the partitions is the result of the difference between the upper bound and the lower bound divided by the number of partitions, that is to say, (upperBound - lowerBound)/partitionNumber, while the first and the last partitions also include all the other rows that are not contained in the other partitions.

For example, to partition 1000 rows into 4 partitions, if you enter 0 for the lower bound and 1000 for the upper bound, each partition will contain 250 rows and so the partitioning is even. If you enter 250 for the lower bound and 750 for the upper bound, the second and the third partition will each contain 125 rows and the first and the last partitions each 375 rows. With this configuration, the partitioning is skewed.


Usage rule

This component is used as a start component and requires an output 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.

Spark Connection

In the Spark Configuration tab in the Run view, define the connection to a given Spark cluster for the whole Job. In addition, since the Job expects its dependent jar files for execution, you must specify the directory in the file system to which these jar files are transferred so that Spark can access these files:
  • Yarn mode (Yarn client or Yarn cluster):
    • When using Google Dataproc, specify a bucket in the Google Storage staging bucket field in the Spark configuration tab.

    • When using HDInsight, specify the blob to be used for Job deployment in the Windows Azure Storage configuration area in the Spark configuration tab.

    • When using Altus, specify the S3 bucket or the Azure Data Lake Storage for Job deployment in the Spark configuration tab.
    • When using on-premise distributions, use the configuration component corresponding to the file system your cluster is using. Typically, this system is HDFS and so use tHDFSConfiguration.

  • Standalone mode: use the configuration component corresponding to the file system your cluster is using, such as tHDFSConfiguration or tS3Configuration.

    If you are using Databricks without any configuration component present in your Job, your business data is written directly in DBFS (Databricks Filesystem).

This connection is effective on a per-Job basis.