[
https://issues.apache.org/jira/browse/NIFI-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017885#comment-16017885
]
Joseph Witt commented on NIFI-3946:
-----------------------------------
Joey in this case I'm suggesting it is a multi condition WHERE clause case.
The nature of the processor is that the result of the lookup goes into a single
RecordPath specified location. I think if we want to offer multiple lookups
and once with different destinations we'll need to have an additional processor
for that use case. Not sure what we'd want to do there for UX such that someone
could have multiple RecordPath pairs for lookup value, replacement target.
But under the nature of the current processor being able to do multi criteria
lookups for a single result will be really powerful. Good case is if I have a
geo of lat and lon I can grab both values and do a lookup that gives me a
reverse geo code. This goes very nicely with the scripted lookup service.
> 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)
