You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2023/11/03 21:30:00 UTC
[jira] [Assigned] (NIFI-12261) Rename Hortonworks Schema Access Strategy pieces
[ https://issues.apache.org/jira/browse/NIFI-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann reassigned NIFI-12261:
---------------------------------------
Assignee: David Handermann
> Rename Hortonworks Schema Access Strategy pieces
> ------------------------------------------------
>
> Key: NIFI-12261
> URL: https://issues.apache.org/jira/browse/NIFI-12261
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: David Handermann
> Priority: Major
> Fix For: 2.0.0
>
>
> The Hortonworks Schema Registry has been removed for the release of NiFi 2.0. However we have remaining pieces in nifi-standard-record-utils where are defined the schema access strategies.
> * HortonworksAttributeSchemaReferenceStrategy
> * HortonworksAttributeSchemaReferenceWriter
> * HortonworksEncodedSchemaReferenceStrategy
> * HortonworksEncodedSchemaReferenceWriter
> * HortonworksProtocolVersions
> Those classes are referenced in SchemaAccessUtils (nifi-avro-record-utils). We probably want to rename all of this and leverage the migrateProperties feature. We could also just rename the "display name" and not really care about it.
> Having those strategies in an extension point could be an option but is probably not worth the effort.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)