[
https://issues.apache.org/jira/browse/NIFI-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530339#comment-16530339
]
ASF GitHub Bot commented on NIFI-5059:
--------------------------------------
Github user MikeThomsen commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2619#discussion_r199597348
--- Diff:
nifi-nar-bundles/nifi-extension-utils/nifi-record-utils/nifi-avro-record-utils/src/main/java/org/apache/nifi/schema/access/SchemaAccessUtils.java
---
@@ -50,7 +50,7 @@
"The content of the FlowFile contains a reference to a schema in
the Schema Registry service. The reference is encoded as a single "
+ "'Magic Byte' followed by 4 bytes representing the
identifier of the schema, as outlined at
http://docs.confluent.io/current/schema-registry/docs/serializer-formatter.html.
"
+ "This is based on version 3.2.x of the Confluent Schema
Registry.");
-
+ public static final AllowableValue INFER_SCHEMA = new
AllowableValue("infer", "Infer from JSON");
--- End diff --
Probably. I'll go ahead and make that change.
> 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)
