Consistent Behaviors of MDM Search Operators

author
Talend Documentation Team
EnrichVersion
6.4
6.3
6.2
6.1
EnrichProdName
Talend Data Fabric
Talend MDM Platform
task
Data Governance > Retrieving data
EnrichPlatform
Talend MDM Web UI
Talend Studio

Consistent Behaviors of MDM Search Operators

In MDM, the master data records can be stored in a SQL database. Talend MDM platform implementations also include a Staging Area, which is a mirror of the SQL storage area containing the master data records.

The master database supports both full text search and standard SQL search, while the staging database only supports standard SQL search. By default, the full text search mode is used for searching in the master database.

The MDM search operators are mainly involved when setting MDM components (tMDMInput, tMDMViewSearch, and tMDMDelete) or defining views in Talend Studio and using search panels in Talend MDM Web UI.

The behaviors of MDM search operators are consistent across the Talend MDM Web UI and the Talend Studio .

Environment

Talend MDM v6.2.1 and above

Consistent behaviors of MDM search operators

Consistent behaviors of MDM search operators are implemented across the Talend MDM Web UI and Talend Studio .

The tables below summarize the behavior of MDM search operators for their single usage.

The behaviors of some operators might be different when used in combination. A summary documentation on the combined usage is expected to be published in the future.

Search operator behaviors based on field types
Operator Description String field Numeric field Date field Foreign key field Multilingual field Complex type field
Contains [1] Returns a result which contains the word or words entered. Supported and displayed as "contains the word(s)" N/A N/A N/A Supported and displayed as "contains the word(s)" N/A
Joins With This operator is reserved for future use. N/A N/A N/A N/A N/A N/A
Starts With [2] Returns a result which begins with the string entered. Supported N/A N/A N/A Supported N/A
is equal to Returns a result which matches the value entered. Supported Supported Supported and displayed as "equals" Supported N/A N/A
is not equal to Returns a result of any value other than the null value and the value entered. Supported Supported N/A N/A N/A N/A
is greater than Returns a result which is greater than the numerical value entered. N/A Supported Supported and displayed as "is after" N/A N/A N/A
is greater than or equal Returns a result which is greater than or equal to the numerical value entered. N/A Supported N/A N/A N/A N/A
is lower than Returns a result which is less than the numerical value entered. N/A Supported Supported and displayed as "is before" N/A N/A N/A
is lower or equal Returns a result which is less than or equal to the numerical value entered. N/A Supported N/A N/A N/A N/A
contains the sentence [1] Returns one or more results which contain the sentence entered. Supported N/A N/A N/A Supported N/A
whole content contains[1] Performs a plain text search using the specified Xpath field in the selected data container. N/A N/A N/A N/A N/A Supported
is empty or null Returns a result where the field is empty or returns a null value. N/A N/A N/A N/A N/A N/A
Predicate Selects a predicate if you use more than one condition. N/A N/A N/A N/A N/A N/A

[1]: Standard SQL search considers the search content as an integrate phrase to be matched, while full text search interprets the search content as a phrase that contains multiple words and returns records that match any of the words. For example, if the search content is "my first house", full text search considers it as three independent words "my", "first", and "house", while standard SQL search considers it as a phrase "my first house".

[2]: Since 6.2.1, the operator “contains a word starting with” has been changed to “starts with” on the Web User Interface, which is transparent during migration.

Search operator behaviors based on modules
Operator Description Components (tMDMInput, tMDMViewSearch and tMDMDelete) Foreign key picker (google style search) in Web User Interface Foreign key filter defined in Studio Xpath filter for View in role definition in Studio View definition in Studio
Contains [1] Returns a result which contains the word or words entered. Supported Supported Supported Supported Supported
Joins With This operator is reserved for future use. Reserved for future use N/A N/A N/A Supported
Starts With [2] Returns a result which begins with the string entered. Supported N/A Supported Supported Supported
is equal to Returns a result which matches the value entered. Supported N/A Supported Supported Supported and displayed as "="
is not equal to Returns a result of any value other than the null value and the value entered. Supported N/A Supported Supported Supported and displayed as "!="
is greater than Returns a result which is greater than the numerical value entered. Supported N/A Supported Supported Supported and displayed as ">"
is greater than or equal Returns a result which is greater than or equal to the numerical value entered. Supported N/A Supported Supported Supported and displayed as ">="
is lower than Returns a result which is less than the numerical value entered. Supported N/A Supported Supported Supported and displayed as "<"
is lower or equal Returns a result which is less than or equal to the numerical value entered. Supported N/A Supported Supported Supported and displayed as "<="
contains the sentence [1] Returns one or more results which contain the sentence entered. Supported N/A Supported Supported Supported
whole content contains [1] Performs a plain text search using the specified Xpath field in the selected data container. Supported for full text search only N/A Supported for full text search only Supported for full text search only Supported for full text search only
is empty or null Returns a result where the field is empty or returns a null value. Supported N/A Supported Supported Supported
Predicate Selects a predicate if you use more than one condition. Supported N/A Supported Supported Supported

[1]: Standard SQL search considers the search content as an integrate phrase to be matched, while full text search interprets the search content as a phrase that contains multiple words and returns records that match any of the words. For example, if the search content is "my first house", full text search considers it as three independent words "my", "first", and "house", while standard SQL search considers it as a phrase "my first house".

[2]: Since 6.2.1, the operator “contains a word starting with” has been changed to “starts with” on the Web User Interface, which is transparent during migration.

For more information, community users can refer to:

  • Talend Open Studio for MDM User Guide
  • Talend Open Studio Components Reference Guide
  • Talend Open Studio for MDM Web User Interface User Guide
  • Talend Open Studio for MDM Installation and Upgrade Guide;

and platform users can refer to:

  • Talend MDM Platform Studio User Guide
  • Talend Components Reference Guide
  • Talend MDM Web User Interface User Guide
  • Talend MDM Platform Installation Guide .