Comparison Operators
You can use multiple operators for comparison during the matching process.
A match rule contains various key elements and the primary element, usually positioned in a
JSON after the comparator and match token classes, is the rule’s comparison formula.
Depending on the rule type you choose (automatic,
suspect, <custom>, or
relevance_based), it will be a boolean or arithmetic expression
that defines how two match candidates should be compared for similarity. The rule will
use Comparison Operators and Helper Operators (Equals, In, And, Or, and Null Values) as the key components of the
expression.
A rule must have one or more Comparison Operators. There are five to choose from -
Exact, ExactOrNull,
ExactOrAllNull, notExactSame, and
Fuzzy. Details of each are below.
Exact
The Exact operator indicates that you wish the comparison for this attribute to be
considered true if the values tested are exactly the same.
ExactOrNull
true if:
- Both attributes have values AND pass the test for exact OR
- One attribute has a value while the other does not OR
- Both attributes have no values
ExactOrAllNull
true if
- Both entities have values AND pass the test for exact OR
- Both entities have no values
notExactSame
Used only within a negative rule, returns true if the two values are NOT
the same. For more details, see topic Negative Rule.
Fuzzy
The Fuzzy operator indicates that you wish the comparison for the attribute to be
considered true if any values being tested are similar, but not
necessarily identical.