[ 
https://issues.apache.org/jira/browse/NIFI-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783451#comment-17783451
 ] 

David Handermann commented on NIFI-12261:
-----------------------------------------

Following a discussion on the initial pull request 7980, a new approach based 
on new Controller Service interfaces seems like the best way forward. 
Introducing new Schema Reference Reader and Schema Reference Writer service 
interfaces will allow migration for deprecated capabilities, such as reading 
and writing Hortonworks attributes and encoded schema identifier information. 
The new service interfaces can support migration for the Confluent Schema 
Registry [Wire 
Format|https://docs.confluent.io/platform/current/schema-registry/fundamentals/serdes-develop/index.html#wire-format]
 and also open extensibility to other types of encoded schema references.

> Refactor Schema Access Strategy and Remove Hortonworks Properties
> -----------------------------------------------------------------
>
>                 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
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> 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)

Reply via email to