Skip to main content Skip to complementary content

Talend Cloud Data Catalog and Talend Data Catalog Applications

New features and improvements

Feature Description Available in
REST API: improved the GET/lineage/{startingId} function The content name is now displayed for the name attribute if the object is a model.

All Talend Data Catalog licenses

REST API: added the name of the new API functions to be used in the description of the deprecated ones You can now see the name of the new API functions to be used in the description of the deprecated ones.

All Talend Data Catalog licenses

Notable fixes

Issue Description Available in
Embedded Webpage widget: invalid URL when using the URL variables Updated the code to replace the variables in the URL before validating it.

All Talend Data Catalog licenses

REST API: incorrect parent ID for a GCP schema Fixed the parentId element for the objects which are internal models within a multi model.

To get the parent ID, you need to set the context parameter to the ID of the configuration or database model by calling the GET/entities/{objectId} function if the objectId element represents a schema in a multi-model database.

All Talend Data Catalog licenses

Oracle Database (via JDBC) / Oracle ERP Application: Operation starting error: "Got a sql exception: Invalid argument(s) in call: length for setBinaryStream cannot be negative" Fixed the import of very large models in the database.

All Talend Data Catalog licenses

Users: invalid email due to extra spaces Added auto space trimming to the email field.

All Talend Data Catalog licenses

Configuration management: entity does not exist or has been deleted Fixed the problem when browsing a folder in a configuration does not show any models.

All Talend Data Catalog licenses

LDAP authentication: password field need to be encrypted The LDAP password is now encrypted.

All Talend Data Catalog licenses

Remote harvesting server (Over the Web): cannot connect to the server Fixed multiple issues related to the status display of the remote harvesting server:
  • Fixed the PingMimbServer command which was not going to the remote server
  • Fixed an UI issue where two invisible extra characters were added to the URL after // and before the ID of the remote server.

You can apply the patch to the Talend Data Catalog application server and not necessary to the remote harvesting servers.

You need to erase, re-enter and save the URL of any existing Over The Web remote harvesting server in the Manage Server to remove the invisible special characters.

All Talend Data Catalog licenses

OAuth authentication: automatic group assignment not working Fixed the automatic group assignment for Microsoft identity platform OAuth 2.0.

All Talend Data Catalog licenses

Security vulnerability: unauthorized users can access functionality for which they are not authorized Restricted the GetSystemInformation function to the members of the Application Administrators group.

All Talend Data Catalog licenses

Glossary: error when creating a read-only copy "CommandFaultException: Got a sql exception" Fixed the SQL Syntax error.

All Talend Data Catalog licenses

Glossary audit log: history data is lost This update contains a database code upgrade. The audit events are now properly copied when creating or restoring glossary versions.

All Talend Data Catalog licenses

Operations for log deletion: defined retention period not taken Fixed the Delete Logs and Delete System Log operations to respect the detention period correctly.

All Talend Data Catalog licenses

Semantic mapping: redirection to terms coming from a glossary under workflow failed with the error: "Cannot read property 'modelEditable' of null" Corrected the glossary version used in the semantic mapping.

All Talend Data Catalog licenses

Data mapping: cannot add SAP Hana calculation views as a source Added the ability to select a SAP Hana calculation view in the query mapping UI.

All Talend Data Catalog licenses

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!