You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2017/05/22 15:55:04 UTC

[jira] [Updated] (NIFI-3946) Should update LookupRecord to allow multi criteria lookups

     [ https://issues.apache.org/jira/browse/NIFI-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende updated NIFI-3946:
------------------------------
    Fix Version/s: 1.3.0

> 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
>             Fix For: 1.3.0
>
>
> 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)