[
https://issues.apache.org/jira/browse/NIFI-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556418#comment-17556418
]
John Wise commented on NIFI-9422:
---------------------------------
With Cloudera seemingly winding down development of its standalone schema
registry service, in order to incorporate it into CDP, this seems like
something that NiFi could greatly benefit from. While the AvroSchemaRegistry
controller service is a decent intro to schema registries, it's not dynamic.
We have to constantly stop & start every attached reader, writer, and processor
attached to it in order to make any schema changes. That's not ideal in our
production environments.
Confluent's schema registry service isn't ideal either, because it requires
standing up a Kafka stack first, which we don't use or need.
> Add Schema Registry Functionality to NiFi Registry
> --------------------------------------------------
>
> Key: NIFI-9422
> URL: https://issues.apache.org/jira/browse/NIFI-9422
> Project: Apache NiFi
> Issue Type: New Feature
> Components: NiFi Registry
> Reporter: Steven Koon
> Priority: Major
>
> Add functionality for the NiFi Registry to provide registering and accessing
> of Avro and JSON schema. This would extend the NiFi ecosystem further and
> allow admins to use NiFi Registry which they already have to setup for
> versioned flows. It would remove the complex setup of relying on other
> external Registry’s.
>
> With the ability to create versioned schema in NiFi Registry users would not
> have to disable AvroSchemaRegistry which creates downtime for all data flows
> that rely on schema in the AvroSchemaRegistry.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
