Skip to main content Skip to complementary content
Announcements

Talend Cloud Data Catalog and Talend Data Catalog Applications

New features and improvements

Feature Description Available in
Search: text containing wildcard shows some inaccurate results The search has been improved to return accurate results if the search text contains a trailing star ('*').

All Talend Data Catalog licenses

Notable fixes

Issue Description Available in
Test performance script: "Could not find required file" Fixed the System Performance Test operation.

All Talend Data Catalog licenses
Default worksheet / search: "Uncaught TypeError / Cannot read property 'toLowerCase'" Fixed the issue when the group name of a default worksheet was null which crashed the filtering code.

All Talend Data Catalog licenses
LDAP authentication: unable to list user in the search filter Fixed the search filter dialog box to show the LDAP users.

All Talend Data Catalog licenses
LDAP authentication: creating new group assignment always deletes existing one Fixed the update of LDAP group assignment.

All Talend Data Catalog licenses
Overview of glossary term: very slow in loading Improved the loading speed of non ajax dashboard widgets.

All Talend Data Catalog licenses
Data mapping: cannot add SAP BW as source or target Added support for SAP BW in the mapper.

All Talend Data Catalog licenses
Collection: unhandled java error when adding object to collection Fixed a bug when selecting a configuration or repository folder in the Select Entity dialog box.

All Talend Data Catalog licenses
Glossary: cannot remove link for term Disabled the creation of the reference link between a term and its parent category.

All Talend Data Catalog licenses
LDAP authentication: conflicts with Active Directory configured as a forest LDAP query delay has been improved when connecting to the global catalog. You should now use the global catalog only.
When using Active Directory configured as a forest and if a query still returns two results instead of one then there are two possibilities:
  • The sAMAccountName attribute is not unique in the forest. You need to switch to UPN (User Principal Name), as it is guaranteed to be unique compared with the sAMAccountName which is only unique for that domain.
  • The forest is not configured correctly. Two servers believe they are responsible for the DN and there are two entries returned with the same DN. Now, the results by DN are merged and it allows to login.

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!

Leave your feedback here