New features
Last updated: 10/30/2026Big Data
| Feature | Description |
|---|---|
| Update of Spark Batch and Spark Streaming names and icons |
|
| Support for EMR 8.0 with Spark 4.0.2 and EMR 8.1 with Spark 4.1 in Spark Batch Jobs | You can now run your Spark Batch Jobs on an Amazon EMR cluster using Spark
Universal with Spark 4.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 8.0 (Spark 4.0.2) and Amazon EMR 8.1 (Spark 4.1.1). |
Continuous Integration
| Feature | Description |
|---|---|
| Upgrade of Talend CI Builder to version 8.0.40 | The Talend CI Builder is upgraded to version 8.0.40. Use Talend CI Builder 8.0.40 in your CI commands or pipeline scripts from this monthly version onwards until a new version of Talend CI Builder is released. |
Data Integration
| Feature | Description |
|---|---|
| Dependency updates in Google Storage and BigQuery components | The Google Storage and BigQuery components now use updated dependencies. |
| Support for custom HTTP headers in SAP OData components | You can now set custom HTTP headers for requests sent by SAP OData components to meet the requirements of your SAP OData services. |
| Improved tQlikOutput selector behavior | When you reopen the Space or Knowledge base selector, the current value is preselected if it matches an available option. This makes it easier to verify or change the configured value. |
Data Mapper
| Feature | Description |
|---|---|
| AI assistant (Qlik Answers) for tDSQL4JSON | You can now use the AI assistant (Qlik Answers) with the tDSQL4JSON component to generate a DSQL script based on a prompt and a JSON file. |
Data Quality
| Feature | Description |
|---|---|
| New tStandardizeDate component | The tStandardizeDate component standardizes values in one or more date columns by using built-in or custom input patterns. It adds a Date-typed standardized column to the main flow and can route values that cannot be parsed to a reject flow. |
| Migration of geocoding components to Places API (New) | The tGoogleGeocoder, tGoogleAddressRow, and tGoogleMapLookup components now use Places API (New) instead of the legacy Places API XML endpoints. Enable Places API (New) for your project and use an API key configured for it. Existing output schemas and status values are unchanged. |