[jira] [Commented] (NIFI-4644) LookupService should support more than String,String key value pairs

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289723#comment-16289723 ] 

ASF GitHub Bot commented on NIFI-4644:
--------------------------------------

Github user MikeThomsen commented on the issue:

    https://github.com/apache/nifi/pull/2304
  
    @markap14 Have you had a chance to think more this? FWIW, it doesn't seem to break any of the unit tests.


> 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)