Skip to main content

Big Data

Feature

Description

Available in

Support for Standalone mode with Spark Universal 3.4.x You can now run your Spark Batch and Spark Streaming Jobs using Spark Universal with Spark 3.4.x in Standalone mode. You can configure it either in the Spark Configuration view of your Spark Jobs or in the Hadoop Cluster Connection metadata wizard.

When you select this mode, Talend Studio connects to a Spark-enabled customized cluster to run the Job from this cluster.

With the general availability of this feature, HBase is now supported. Note that Hive, and Spark Jobs with Avro components are not supported for the moment.

Spark Configuration view of a Spark Batch Job opened with Standalone mode in Spark 3.4.x highlighted.

All subscription-based Talend products with Big Data

New options available in tHBaseTable New parameters are now available in the Basic settings view of tHBaseTable:
  • Family parameters, which replaces Families, and allows you to specify more characteristics for the family parameters.
  • Split regions keys allows you to split tables by regions keys manually.
Basic settings view of tHBaseTable opened highlighting Family parameters and Split regions keys options.

All subscription-based Talend products with Big Data

Support for Databricks runtime 13.x with Spark Universal 3.4.x
Availability-noteBeta contentBeta
You can now run your Spark Batch and Streaming Jobs on job and all-purpose Databricks clusters on Google Cloud Platform (GCP), AWS, and Azure using Spark Universal with Spark 3.4.x. You can configure it either in the Spark Configuration view of your Spark Jobs or in the Hadoop Cluster Connection metadata wizard.

When you select this mode, Talend Studio is compatible with Databricks 13.x version.

Spark Configuration view of a Spark Batch Job opened with Databricks mode in Spark 3.4.x highlighted.

All subscription-based Talend products with Big Data

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 – let us know how we can improve!