Skip to main content Skip to complementary content

Talend Data Catalog 8.1

New Or Improved Features

  1. If the search index is a Solr index, you can order your query results not only by Name, Relevance and "Updated Date" but also by other property types:
    • System attributes. Note: Only the system attributes that are stored in the search index can be used as the order by fields. Besides multi-valued system attributes such as "Data Classifications" or object-valued system attributes such as "Column Statistics" cannot be used as an order by field
    • Custom attributes. Note: Custom attributes of the Enumeration (Multi-value), Users, Rich Text, Blob or Multiline Text type cannot be used as an order by field. Order by a custom attribute of the User data type returns the results sorted by the user ids not by the usernames.
    • Profile attributes
    • Data Profiling attributes except the multi-valued attribute "Data Profiling"."Inferred Data Types"
    • UDPs

You can have more than one order by field in the Order By clause. Each field can be a property type in the above list with its own asc(ending) or desc(ending) order. For example, "Last Name" asc, "First Name" desc. This sorts everything by "Last Name" in the ascending order first and then by "First Name" in the descending order whenever the "Last Name" property for two or more objects are identical.

  1. New system attributes are added: Model, "Source System Definition", "Data Select Method", "Data Select Query", "Replication Quality", "Imported Date", Source, Destination, "Source Model" and "Destination Model".
  2. The system attribute "Business Name" is now a custom attribute of an imported object (e.g. Table)
  3. The system attribute "Content Name" is renamed to "Model Name", and "Content Description" to "Model Definition". The system attribute "External URL" is renamed to "Open In Tool". The system attribute "Description" is renamed to "System Description". "Description" replaces the custom attribute "Long Description" as HTML formatted text of unlimited length that can include images, tables, etc.
  4. The filter type CONTENT is converted to a system attribute Model.
  5. Support of binary complex relationships in the SELECT list and WHERE clause.
  6. Support of faceting on certain system attributes and custom attributes if the search index is a Solr index.
  7. Support of subquery =WHERE(<subquery>) or !=WHERE(<subquery>) filters on the system attribute Model or custom relationship.

Deprecated features do not require any action before upgrading to MM 11.1.0. If any of these features are used in worksheets, dashboards, conditional labels and collections created in the previous release, they will be automatically upgraded. In order to use any of these features in MQL queries in the REST API functions, you need to set the mqlVersion parameter to 1 or 2 so that they can be automatically upgraded. If you use any deprecated feature in the filters entered manually, you may get a warning about the field cannot be resolved to a valid attribute, in which case, you will need to replace the deprecated feature with the new feature by yourself.

Deprecation of features


More information

"Business Description" system attribute

Custom attribute Definition

Naming standardization. Removal is considered for MM 12.0

Custom attribute "Long Description"

Custom attribute Description

Naming standardization. Removal is considered for MM 12.0

"Content Name" system attribute

"Model Name" system attribute

Naming standardization. Removal is considered for MM 12.0

"Content Description" system attribute

"Model Definition" system attribute

Naming standardization. Removal is considered for MM 12.0

CONTENT filter type

Model system attribute

Naming standardization. Removal is considered for MM 12.0

Scope filter in the FROM clause

Model=WHERE(…) in the WHERE clause

MQL normalization

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!