[
https://issues.apache.org/jira/browse/NIFI-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017927#comment-16017927
]
Joey Frazee commented on NIFI-3946:
-----------------------------------
What you describe makes a lot of sense if you're trying to do a single
enrichment on a wide dataset (relational DBs, CSV files), but the simple CS's
at least are also really useful for doing a bunch of independent attribute
enrichments (on flat, narrow key-value stores; e.g., caches, properties files)
in one go [1]. In the LookupAttribute processor here, the name of the dynamic
property is the destination attribute name and the value is the key for the
lookup (potentially an attribute expression).
So in [1] I took something really dumb like properties files as the base case
and then for the DBs and CSV files you specify a key column and value column
and it operates like a KV store.
Either way, if multi-criteria is the base case, then we need to at least have a
sub-class to allow for a more KV-like lookup.
1. https://issues.apache.org/jira/browse/NIFI-3404
> Should update LookupRecord to allow multi criteria lookups
> ----------------------------------------------------------
>
> Key: NIFI-3946
> URL: https://issues.apache.org/jira/browse/NIFI-3946
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Joseph Witt
> Assignee: Mark Payne
>
> At present the LookupRecord processor allows a single criteria lookup.
> We need to provide a lookup API which takes a map of string key/values that a
> given lookup can use when searching for the result. The LookupRecord
> processor should change such that all dynamic properties are the loookup key
> names with values that are the RecordPath to find the value for that given
> key. The resulting map would be passed to the lookup service. Also the lookup
> service API should allow returning the set of required key names so that the
> processor can validate once all required keys have RecordPaths to search for
> values.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
