Talend Data Catalog Application - 7.3

Talend Data Catalog Release Notes

EnrichVersion
7.3
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
EnrichPlatform
Talend Data Catalog
task
Data Governance
Release Notes

New features and improvements

Feature Description
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 ('*').

Notable fixes

Issue Description
Test performance script: "Could not find required file" Fixed the System Performance Test operation.
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.
LDAP authentication: unable to list user in the search filter Fixed the search filter dialog box to show the LDAP users.
LDAP authentication: creating new group assignment always deletes existing one Fixed the update of LDAP group assignment.
Overview of glossary term: very slow in loading Improved the loading speed of non ajax dashboard widgets.
Data mapping: cannot add SAP BW as source or target Added support for SAP BW in the mapper.
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.
Glossary: cannot remove link for term Disabled the creation of the reference link between a term and its parent category.
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.