# New features

## Shared features

| Feature | Description |
| --- | --- |
| New Talend Studio<br>release lifecycle | You can now choose a monthly release or a support release when updating<br>Talend Studio.<br>Monthly releases include new features, improvements, bug fixes, and security<br>updates. Support releases include CVE and support issue fixes without new and<br>preview features. For more information, see [Understanding the update lifecycle for Talend Studio](https://help.qlik.com/talend/en-US/installation-guide-windows/8.0/studio-update-lifecycle). |
| Enhancement of AI assistant (Qlik Answers) in Talend Studio | You can now use the AI assistant in Talend Studio<br>to modify both input and output schemas in the tMap component. It can add, remove,<br>or rename columns and update column properties, so you can make schema changes<br>without editing each table manually. |

## Big Data

| Feature | Description |
| --- | --- |
| Update of Spark Batch and Spark Streaming names and icons | <ul> <li>In the repository view, <span>Big Data Batch</span> and                           <span>Big Data Streaming</span> under <span>Job                           Designs</span> are now named <span>Spark Batch</span> and                           <span>Spark Streaming</span>.</li> <li>In the Metadata repository view, <span>Big Data                           Configurations</span> is now <span>Spark Cloud                           Configurations</span>.</li> <li>For Structured Streaming Jobs, the <span>Run</span> tab now shows                           <span>Spark Configuration</span> instead of                           <span>Structured Streaming Configuration</span>.</li> <li>Spark Batch, Spark Streaming, and Joblet now use updated icons.</li> </ul> |
| Support for EMR 8.0 with Spark 4.0.2 and EMR 8.1 with Spark 4.1 in Spark<br>Batch Jobs | You can now run your Spark Batch Jobs on an Amazon EMR cluster using Spark<br>Universal with Spark 4.x in Yarn cluster mode. You can<br>configure it either in the Spark Configuration view of your<br>Spark Jobs or in the Hadoop Cluster Connection metadata<br>wizard.<br><br>When you select this mode, Talend Studio is compatible with Amazon EMR 8.0 (Spark 4.0.2) and Amazon EMR 8.1 (Spark<br>4.1.1). |

## Continuous Integration

| Feature | Description |
| --- | --- |
| Upgrade of Talend<br>CI Builder to version 8.0.40 | The Talend<br>CI Builder is upgraded to version 8.0.40. Use Talend<br>CI Builder 8.0.40 in your CI commands or pipeline scripts from this monthly<br>version onwards until a new version of Talend<br>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<br>dependencies. |
| Support for custom HTTP headers in SAP OData components | You can now set custom HTTP headers for requests sent by SAP OData<br>components to meet the requirements of your SAP OData services. |
| Improved tQlikOutput selector behavior | When you reopen the Space or Knowledge<br>base selector, the current value is preselected if it matches an<br>available option. This makes it easier to verify or change the configured<br>value. |

## Data Mapper

| Feature | Description |
| --- | --- |
| [Preview](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Introduction/feature-preview-program-overview.htm)<br><br>AI assistant (Qlik Answers) for tDSQL4JSON | You can now use the AI assistant (Qlik Answers) with the tDSQL4JSON<br>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<br>one or more date columns by using built-in or custom input patterns. It adds a<br>Date-typed standardized column to the main flow and can route values that cannot<br>be parsed to a reject flow. |
| Migration of geocoding components to Places API (New) | The tGoogleGeocoder,<br>tGoogleAddressRow, and<br>tGoogleMapLookup components now use Places API (New) instead<br>of the legacy Places API XML endpoints. Enable Places API (New) for your project<br>and use an API key configured for it. Existing output schemas and status values<br>are unchanged. |