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/04/26 14:22:01 UTC
[jira] [Updated] (NIFI-5123) Enable extensions to use
SchemaRegistryService
[ https://issues.apache.org/jira/browse/NIFI-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated NIFI-5123:
-------------------------------
Status: Patch Available (was: In Progress)
> Enable extensions to use SchemaRegistryService
> ----------------------------------------------
>
> Key: NIFI-5123
> URL: https://issues.apache.org/jira/browse/NIFI-5123
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> Currently SchemaRegistryService is in the nifi-record-serialization-services NAR, which means that other extensions (unless they had nifi-record-serialization-services-nar as a parent which is not recommended) cannot make use of this abstract class. The class uses utilities from nifi-avro-record-utils such as SchemaAccessUtils, and is a very helpful base class used to offer a consistent user experience for selecting schemas (by name, by test, from a schema registry, etc.). Other extensions wishing to provide access to a schema registry would duplicate much of the logic in SchemaRegistryService, which offers challenges for consistency and maintainability.
> This Jira proposes to move SchemaRegistryService into nifi-avro-record-utils, where it can be leveraged by any extension that depends on it, and thus we can strongly recommend that record-aware processors that will interact with a schema registry use SchemaRegistryService as a parent class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)