[
https://issues.apache.org/jira/browse/NIFI-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981751#comment-15981751
]
ASF GitHub Bot commented on NIFI-3682:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/1682
Soooo close. "schema registry is invalid because schema.name is set and
scheme registry is not..." paraphrasing a bit there. Looks like validation on
that is alittle buggy. I'm using the GrokReader without a schema registry set
and this is what pops up now. All else looks solid. Pretty sure this will
wrap it up.
> Add "Schema Access Strategy" to Record Readers and Writers
> ----------------------------------------------------------
>
> Key: NIFI-3682
> URL: https://issues.apache.org/jira/browse/NIFI-3682
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.2.0
>
>
> Currently the record readers are mostly configured with a Schema Registry
> service and the name of the schema. We should instead allow user to choose
> one of several strategies for determining the schema: Schema Registry +
> schema.name attribute, Schema Registry + identifier and version embedded at
> start of record/stream, avro.schema attribute, embedded schema for cases like
> Avro where the schema can be embedded in the content itself.
> On the writer side, we should also expose these options in order to convey
> the schema information to others.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
