You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2019/04/01 16:32:04 UTC
[jira] [Commented] (NIFI-5338) Add ScriptedLookupService Support to
LookupAttribute
[ https://issues.apache.org/jira/browse/NIFI-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806961#comment-16806961 ]
Matt Burgess commented on NIFI-5338:
------------------------------------
AFAICT StringLookupService is there to filter out the LookupService implementations that return complex objects like Map or Record, so the user doesn't get to choose a service that can give unexpected results. Currently the pattern is to provide two services, one that implements StringLookupService, and one that implements something like LookupService<Record> for example.
I'm thinking the way to go here is to add a SimpleScriptedLookupService, what do you think?
> Add ScriptedLookupService Support to LookupAttribute
> ----------------------------------------------------
>
> Key: NIFI-5338
> URL: https://issues.apache.org/jira/browse/NIFI-5338
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Shawn Weeks
> Priority: Minor
>
> I'm working on a project where I need to lookup attributes in an external database. Currently I'm using a custom ExecuteGroovyScript but it would be really useful if LookupAttribute supported the ScriptedLookupService. LookupAttribute probably could just check that string is returned and accept any LookupService instead of requiring a StringLookupService.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)