New features
Big Data
Feature | Description |
---|---|
Improvement of Spark Universal user interface | The Spark Universal user interface is changed. You now have to select first the Runtime/mode environment, and then the Version. |
Support for Kubernetes with Spark 3.1.x to 3.5.x versions | You can now run your Spark Jobs on Kubernetes mode with Spark 3.1.x to 3.5.x versions, with the new Spark 3.x option in the Version drop-down list. You can configure it either in the Spark Configuration view of your Spark Jobs or in the Hadoop Cluster Connection metadata wizard. |
Support for Amazon EMR 7.x with Spark Universal 3.5.x | You can now run your Spark Jobs on an Amazon EMR cluster using Spark
Universal with Spark 3.5.x in Yarn cluster 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 is compatible with Amazon EMR 7.x version. |
Data Integration
Feature | Description |
---|---|
tOpenAIClient component in Standard Jobs (GA) |
The tOpenAIClient component becomes generally available from 8.0
R2023-09. For more information, read the tOpenAIClient documentation. |
New Solr components in Standard Jobs |
The following Solr components are now available to read and write from an
Apache Solr web service:
For more information, read the Solr documentation. |
New tPineconeClient component in Standard Jobs |
The new tPineconeClient component allows you to upsert, query, fetch,
update, or delete records in Pinecone index namespaces. For more information, read the tPineconeClient documentation. |
Data Mapper
Feature | Description |
---|---|
Support for map export as CSV or Excel files | You can now export a Standard map as a CSV file, with the new
Maps as CSV option. The exported file is also compatible
with Excel. For more information, see Exporting a map. |
Improvement of output name generation with flattening map | When you create a flattening map with multiple outputs, the output naming is
improved. The generated output naming is now made after the input source element.
For more information on the naming conventions, see Flattened structure naming. |