Skip to main content Skip to complementary content

tGSConfiguration properties for Apache Spark Batch

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

The Spark Batch tGSConfiguration component belongs to the Storage family.

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

Basic settings

When you use this component with Google Dataproc:

Google Storage bucket

Enter the name of the bucket to be used by the whole Job. Then the File components such as tFileInputDelimited or tFileOutputDelimited use the directories in this bucket.

For example, if you enter my_bucket in this field and enter /user/ychen in the Folder field of tFileInputDelimited, tFileInputDelimited reads data from gs://my_bucket/user/ychen.

When you use this component with other distributions:

Project ID

Enter the ID of your Google Cloud Platform project.

If you are not certain about your project ID, confirm it in the Manage Resources page of your Google Cloud Platform services.

Google Storage bucket

Enter the name of the bucket to be used by the whole Job. Then the File components such as tFileInputDelimited or tFileOutputDelimited use the directories in this bucket.

For example, if you enter my_bucket in this field and enter /user/ychen in the Folder field of tFileInputDelimited, tFileInputDelimited reads data from gs://my_bucket/user/ychen.

Use P12 credentials file format

When the Google credentials file to be used is in P12 format, select this check box and then in the Service account Id field that is displayed, enter the ID of the service account for which this P12 credentials file has been created.

Path to Google Credentials file

Enter the path to the credentials file associated to the user account to be used. This file must be stored in the machine in which your Talend Job is actually launched and executed.

If you use Talend JobServer to run your Job, store the credentials file not only in the machine of the Talend JobServer, in which the Job is launched, but also in the worker machines of the Spark cluster, in which the Job is executed; if you do not use the Talend JobServer, store the credentials file in your local machine from which you launch the Job and in the worker machines of the Spark cluster.

Global Variables

Global Variables

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 more information about variables, see Using contexts and variables.

Usage

Usage rule

You can use multiple tGSConfiguration components in one Job to provide connection configuration to Google Storage.

For example, using two tGSConfiguration components in one Job allows you to use different Google Storage buckets with different credentials. To use two tGSConfiguration components, you need to set up the right permissions in the Google Storage console > Bucket > Permissions > Roles.

For example, if you are working on:
  • project-1234 with userX@project-1234.iam.gserviceaccount.com and userX_bucket
  • project-4567 with userY@project-4567.iam.gserviceaccount.com and userY_bucket
You will need to:
  • add userX@project-1234.iam.gserviceaccount.com as Storage Admin to userY_bucket and point to project-4567
  • add userY@project-4567.iam.gserviceaccount.com as Storage Admin to userX_bucket and point to project-4567
For more information about IAM permissions, see the Google Storage documentation.

From R2022-12 onwards of Talend Studio 8.0, tGSConfiguration supports Spark Universal in the Local mode and Databricks on Google Cloud Platform.

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-premises 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 Apache Spark Batch or tS3Configuration Apache Spark Batch.

    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.

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!

Leave your feedback here