[
https://issues.apache.org/jira/browse/NIFI-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017785#comment-16017785
]
ASF GitHub Bot commented on NIFI-3938:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1828
Built with `contrib-check` and all tests pass. With Matt's help, I created
a schema registry with a defined schema, generated flowfiles with CSV formatted
data (a hockey roster), and used `SplitRecord` with the `CSVReader` and
`CSVRecordSetWriter` controller services to split the data into individual
flowfiles, then used `LookupRecord` with `ScriptedLookupService` and wrote a
custom Groovy implementation which performed position lookups. Finally, I
output the enriched flowfiles to a `ConvertRecord` processor which wrote them
out in JSON.
Looks very useful and I think this will make a lot of people's flows more
powerful. Thanks Matt.
+1, merging.
> Add a ScriptedLookupService
> ---------------------------
>
> Key: NIFI-3938
> URL: https://issues.apache.org/jira/browse/NIFI-3938
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
>
> NIFI-3863 aims to implement a LookupRecord processor along with two
> implementations of LookupServices, one for enriching records with Geo
> information from IP addresses, and a static one from a list of provided
> key/value pairs.
> A very flexible and powerful improvement would be to offer a
> ScriptedLookupService, where the same scripting capabilities that are
> available to InvokeScriptedProcessor, ScriptedReader and
> ScriptedRecordSetWriter are available to prototype/implement a LookupService
> for use by the LookupRecord processor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
