Talend Studio
The R2020-04 Studio monthly update contains new features and bug fixes.
This monthly release also includes all changes and fixes from the previous 7.3 monthly releases. For a full list of new features and bug fixes, see Changelog for R2020-04.
The new features and bug fixes lists are for Talend Data Fabric. The exact content changes based on your license.
To obtain the Studio monthly update, you need to submit a request via Talend Support portal.
- All Talend Studio clients connected to the same project must have the same monthly update installed. Updating a Studio connected to a project requires all the Studios connected to that project to be updated.
- Before applying a patch, be sure to create a backup tag or a backup branch with the current Talend version.
Big Data: new features
|
Feature |
Description |
Available in |
|---|---|---|
|
Delta Lake metastore support for Spark Jobs |
You can now interact with the Delta Lake metastore when using the Delta Lake components for read or write operations in Spark Batch. |
All Talend products with Big Data |
Data Integration: new features
|
Feature |
Description |
Available in |
|---|---|---|
|
New options provided by tWriteXMLField, tCosmosDBOutput, and tMongoDBOutput |
|
All Talend products with Talend Studio |
Data Mapper: new features
|
Feature |
Description |
Available in |
|---|---|---|
| Flattening map | The flattening feature has been improved and now
automatically maps your input hierarchical structure with a new flat output
structure.
|
All Talend Platform and Data Fabric products |
| LoopIndex properties | The LoopIndex function has new properties which allow you to configure the index calculation on an input or output loop. |
All Talend Platform and Data Fabric products |
| CSV representation properties | A new property in the CSV representation allows you to select whether you want to include the _osdtTerminator field in your structure. |
All Talend Platform and Data Fabric products |
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!