Skip to main content

Talend Data Catalog: migration

Item Description

Available in

Talend Data Catalog upgrade to 8.0 Talend Data Catalog 8.0 requires a new installation. Follow the migration steps as described in Migrating Talend Data Catalog 7.3 to 8.0.

All Talend Data Catalog licenses

Glossary migration process The repository database upgrade includes a Migrate Glossaries to Metamodel operation.
  • The Category objects from previous versions are now migrated as terms without losing the hierarchy at the instance level.
  • The predefined and hard-coded relationships between terms from previous versions such as More General/More Specific, Contains/Contained by, Represents/Represented by, References/Referenced by, See Also are migrated as part of an optional Glossary Extension (MM) package without loss. These relationships are not a mandatory part of the Standard package, as you can now define better custom relationships with appropriate names.
  • The glossary terms had two workflow related properties in previous versions. Status has been renamed Workflow State with the same values (Candidate, Draft, Under Review, Pending Approval, Approved, Published, and Deprecated) and State (Deprecated, New, and Published) is replaced with Workflow Published (True/False) and Workflow Deprecation Requested (True/False).
  • The Abbreviation attributes are migrated to a new Has Acronym relationship to a new Acronym object. The Alternative Abbreviation attributes are not migrated.
  • The categories and terms were used to implement naming standards, which are now implemented by a Naming Standards model. This model contains Naming Standard objects including Naming objects.

    When enabling the naming standards, you now have to select which Naming Standard object you want to use instead of a glossary category. The Migrate Glossaries to Metamodel operation also migrates any categories and terms used for naming standards into new objects of the Naming Standards model.

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!