Skip to main content

Deprecated API Methods, Parameters or Schemas

Deprecated API methods, parameters or schemas do not require any action before upgrading to Talend Data Catalog 8.0. They will continue to work as normal in Talend Data Catalog 8.0. We plan to remove them in the next major release.

Deprecation of API methods, parameters, or schemas

Replacements

More information

POST /repository/databaseDocumentation/exportCSV

POST /repository/model/export

Consolidate the import/export APIs

GET /repository/semanticTypes

GET /repository/dataClasses

Rebrand "Semantic Type" as "Data Class"

GET /repository/semanticTypes/{objectId}

GET /repository/dataClasses/{objectId}

Rebrand "Semantic Type" as "Data Class"

PUT /repository/semanticTypes/{objectId}

PUT /repository/dataClasses/{objectId}

Rebrand "Semantic Type" as "Data Class"

POST /entities/executeMQLQuery parameter legacyEntityFormat

This function will always return results in the MQL Entity Format

POST /entities/getAttributeDistinctValueCounts

POST /entities/getAttributeValueCounts

The new function is more efficient

POST /entities/getInferredSemanticObjects

POST /entities/executeMQLQuery

Use the system attribute "Inferred Documentation" to get inferred documentation of the object

POST /dataMapping/exportExcel

POST /dataMapping/exportScript

The output of the new function can be edited by the user and imported back via POST /dataMapping/importScript

POST /entities/DataProfiling/{objectId} parameter hideData

new parameter sensitivityLabel

Use sensitivity label to hide data

GET /types/listEntityTypes

GET /types/listObjectTypes

Rebrand entity type as object type

GET /repository/customAttributes/{nameOrId}

POST /repository/metaModel/exportXML

Rebrand custom attributes as Meta model attribute types. Export the Meta model to view the definition of any attribute type.

POST /operations/glossary/exportAndDownloadCSV

POST /repository/model/export

Specify the objectIds parameter to export a term or a list of terms.

PUT /repository/setCustomAttributes

PUT /repository/setAttributes

Rebrand custom attributes as Meta model attribute types

GET /entities/DataProfiling/{objectId}

Deprecated the following fields in the result: totalSemanticTypeRows, invalidSemanticTypeValues and inferredSemanticTypes.

Removed data classes from data profiling. Note that these fields are not set in the output.

PUT /entities/DataProfiling/{objectId}

Deprecated the following fields in the Request body: totalSemanticTypeRows, invalidSemanticTypeValues and inferredSemanticTypes.

Removed data classes from data profiling. Note that these fields in the input will be ignored.

POST /entities/glossary parameter categoryPath

new parameter termPath

Removed category from glossary

GET /types/listAttributeTypes parameter entityType

new parameter objectType

Rebrand entity type as object type

GET /types/listGroupTypes parameter entityType

new parameter objectType

Rebrand entity type as object type

Schema Entity's field entityType

new field objectType

Rebrand entity type as object type. Note that entityType and objectType are set to the same value for MM 11.0.

Schema Entity's field term

new field terms

Object can be defined by multiple terms. The field term will store the first term if the object has multiple terms.

Schema Entity's field semanticTypes

new field dataClassifications

Rebrand semantic type as data classification. Note that semanticTypes and dataClassifications are set to the same value for MM 11.0.

Enumeration type ReferenceType used by Schema GlossaryTermReference's type field

Replaced "More General" with "Specializes", "More Specific" with "Generalizes". Added "Possible Value" and "Possible Value Of".

New meta model relationships for Term

Schema ModelSettings_Create's field "Send email notification when an import"

Notifications are sent to model watchers for model changes and metadata managers for import failures. There are no more notification options in the content.

Schema ModelSettings_Create_Data's field "Data hiding"

new field "Hide data using Sensitivity Label"

Data hiding is controlled by the sensitivity label defined on the field

Schema ModelSettings_Set's field "Send email notification when an import"

Notifications are sent to model watchers for model changes and metadata managers for import failures. There are no more notification options in the content.

Schema LIneageLink’s field lineageType

new field lineageTypeText

Switched from the integer field lineageType to the string field lineageTypeText to be more descriptive.

Schema LineageNode’s field modifiers

It is not useful for the users

Schema LineageTree’s field text

It is not useful for the users

The field of hideData in the schemas: DataClass and DataClassWithStatus

new field sensitivityLabel

Use sensitivity label to hide data

GET /repository/dataClasses parameter hideDataOption

new parameter sensitivityLabelOption

Use sensitivity label to hide data

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 – please let us know!