tSetKeystore properties in Spark Batch Jobs - 6.1

Talend Components Reference Guide

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
Talend Studio
Data Governance
Data Quality and Preparation
Design and Development

Component family



Basic settings

TrustStore type

Select the type of the TrustStore to be used. It may be PKCS 12 or JKS.


TrustStore file

Type in the path, or browse to the certificate TrustStore file (including filename) that contains the list of certificates that the client trusts.


TrustStore password

Type in the password used to check the integrity of the TrustStore data.


Need Client authentication

Select this check box to validate the keystore data. Once doing so, you need complete three fields:

- KeyStore type: select the type of the keystore to be used. It may be PKCS 12 or JKS.

- KeyStore file: type in the path, or browse to the file (including filename) containing the keystore data.

- KeyStore password: type in the password for this keystore.


Check server identity

Select this check box to make the Job verify the match between the hostname of the URL and the hostname of the server. If they mismatch, the verification mechanism asks whether this connection should be allowed.

Usage in Spark Batch Jobs

In a Talend Spark Batch Job, this component is used standalone. It generates native Spark code that can be executed directly in a Spark cluster.

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

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.


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.