Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: mmarinelliNode Name: Substring Lookup
Node Category: Correlation
Use Case: Use this node to look up field values which don't match exactly but which have matching substrings
Tested on Release: 4.1.7
External Dependencies: None
Practical Usage Example: An example use of this node has been provided in the prototype examples graph which is released in conjunction with the prototype library. Please see that graph for a executable use case.*
Node Documentation:
Functional Description:
Compares field values from two sources using multiple substring matching techniques, producing an output row for each record in the "main" input for which any record in the "lookup" input matches. Matching conditions for each technique are described below:
- "starts with": The key value in the "main" input starts with one or more values in the "lookup" set. Example: main = 'Absolute' and lookup = 'ab' or 'abs'
- "ends with": The key value in the "main" input ends with one or more values in the "lookup" set. Example: main = 'Absolute' and lookup = 'te' or 'ute'
- "contains": The key value in the "main" input contains one or more values in the "lookup" set. Example: main = 'Absolute' and lookup = 'te' or 'ute' or 'sol' or 'bso'
The output contains two new fields:"MATCH_KEY" - the list of lookup values which matched"MATCH_TYPE" - the test used to compare the inputs; one of: 'starts with', 'ends with', 'contains'
-
InputKey: Field from "main" input which will be compared to "lookup" input
-
LookupKey: Field from "main" input which will be compared to "lookup" input
-
MatchType: Matching condition; one of "starts with", "ends with", "contains"
-
CaseSensitive: If True, matches will be case sensitive. Defaults to False.
Known Limitations: None