[
https://issues.apache.org/jira/browse/NIFI-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270943#comment-16270943
]
ASF GitHub Bot commented on NIFI-4644:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2304
@MikeThomsen I am just a bit concerned about potential implications of this
change... at first glance I don't see any particular problem with it, but I
feel like there may be a condition that I am overlooking... It is probably
okay, but I would like to think about this just a bit more.
> 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
>
> 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)
