Consistent behaviors of MDM search operators - 6.2

Talend MDM Platform Release Notes

EnrichVersion
6.2
EnrichProdName
Talend MDM Platform
task
Installation and Upgrade
EnrichPlatform
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend DQ Portal
Talend ESB
Talend Identity Management
Talend Installer
Talend JobServer
Talend Log Server
Talend MDM Server
Talend MDM Web UI
Talend Project Audit
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio

The behaviors of MDM search operators are now consistent across Talend MDM Web User Interface and Talend Studio.

Note that both full text search and standard SQL search are supported in the master database, while only standard SQL search is supported in the staging database.

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.

Table 1. 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 an empty field or 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 which contains multiple words, and the records that match any of the words will be returned. For example, if the search content is "test first name", full text search will consider it as three independent words "test", "first", and "name", while standard SQL search will consider it as one phrase "test first name".

[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.

Table 2. 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 an empty field or 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 which contains multiple words, and the records that match any of the words will be returned. For example, if the search content is "test first name", full text search will consider it as three independent words "test", "first", and "name", while standard SQL search will consider it as one phrase "test first name".

[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.