You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2018/05/30 13:04:00 UTC
[jira] [Updated] (NIFI-5059) MongoDBLookupService should be able to
determine a schema or have one provided
[ https://issues.apache.org/jira/browse/NIFI-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated NIFI-5059:
-------------------------------
Status: Patch Available (was: Open)
> 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)