[jira] [Commented] (NIFI-5059) MongoDBLookupService should be able to determine a schema or have one provided

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

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

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

Github user MikeThomsen commented on the issue:

    https://github.com/apache/nifi/pull/2619
  
    @pvillard31 @mattyb149 I updated this to have a clean separation between the controller and lookup service code and subclassed the lookup service from SchemaRegistryService. Can one of you do a review sometime soon?


> MongoDBLookupService should be able to determine a schema or have one provided
> ------------------------------------------------------------------------------
>
>                 Key: NIFI-5059
>                 URL: https://issues.apache.org/jira/browse/NIFI-5059
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Mike Thomsen
>            Assignee: Mike Thomsen
>            Priority: Major
>
> MongoDBLookupService should have two schema handling modes:
>  # Where a schema is provided as a configuration parameter to be applied to the Record object generated from the result document.
>  # A schema will be generated by examining the result object and building one that roughly translates from BSON into the Record API.
> In both cases, the schema will be applied to the Mongo result Document object that is returned if one comes back.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)