[ https://issues.apache.org/jira/browse/NIFI-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016940#comment-16016940 ]
ASF subversion and git services commented on NIFI-3863: ------------------------------------------------------- Commit 9bd0246a96cfcda01b972834823250a9cddf77a8 in nifi's branch refs/heads/master from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=9bd0246 ] NIFI-3863: Initial implementation of Lookup Services. Implemented LookupRecord processors. This required some refactoring of RecordSetWriter interface, so refactored that interface and all implementations and references of it > Create a LookupRecord Processor > ------------------------------- > > Key: NIFI-3863 > URL: https://issues.apache.org/jira/browse/NIFI-3863 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions > Reporter: Mark Payne > Assignee: Mark Payne > Fix For: 1.3.0 > > Attachments: template-for-lookup-parition-provenance-records.xml > > > We should provide a mechanism to fetch a value from a Record, and then lookup > that value in a "lookup table." If we get a match, we should add the result > back into a field in the Record. > The Processor would be configured with a Record Reader and a Record Writer. > It would also take a RecordPath as a 'Lookup Path' that indicates where in > the Record the desired value should be pulled from. We then lookup the value > from that field. There should also be a 'Destination Path' property that > indicates where the value should be added back to the record. The record > should then be routed to either a 'matched' relationship if there was a value > in the lookup table, or an 'unmatched' relationship if there was no value in > the lookup table. > The 'Destination Path' property should be optional. This way, if it is set, > this Processor would function as an 'enrichment processor.' If the property > is not set, this Processor would function as a 'routing processor', by > routing to either 'matched' or 'unmatched' depending on whether or not its > value is found in the Lookup Table. > This means that we also need to build a Lookup Table type of Controller > Service. It would be best to provide two implementations: a Properties > File-based lookup service and a Simple Key-Value Lookup Service. The Simple > Key-Value service would just allow the user to add properties where the > Property Name is the Key and the Property Value is the value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)