You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2017/12/13 21:08:00 UTC
[jira] [Resolved] (NIFI-4644) LookupService should support more
than String,String key value pairs
[ https://issues.apache.org/jira/browse/NIFI-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne resolved NIFI-4644.
------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
> LookupService should support more than String,String key value pairs
> --------------------------------------------------------------------
>
> Key: NIFI-4644
> URL: https://issues.apache.org/jira/browse/NIFI-4644
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Fix For: 1.5.0
>
>
> The current interface is:
> {code:java}
> T lookup(Map<String, String> coordinates)
> {code}
> Limiting that to String, String has already caused problems for people using the MongoDBLookupService. For example, a user wanting to do a lookup using a String/Integer combination will find that the type is converted to String/String automatically and it will fail against any data source that cannot automatically make that conversion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)