[
https://issues.apache.org/jira/browse/NIFI-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530684#comment-16530684
]
ASF GitHub Bot commented on NIFI-5059:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2619
+1 LGTM, one of the unit tests in Travis is failing but it's not the fault
of this code. I ran the unit tests and some tests on a live NiFi instance with
"Infer" and "Schema Text" strategies, all looked well. Thanks for the addition!
Merging to master
> 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)
