[
https://issues.apache.org/jira/browse/AVRO-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740521#comment-17740521
]
Christophe Le Saec commented on AVRO-2918:
------------------------------------------
I just made [this second PR|https://github.com/apache/avro/pull/2322] that
change code generation to integrate inheritance feature.
As explain in precedent comment, i had to modify generated code to avoid issues
with static methods; so, new generated code is not compatible with current;
client code will need to be modify; as
{code:java}
GeneratedType.CODER.fromByteBuffer(b); // instead of
GeneratedType.fromByteBuffer(b);
GeneratedType.getClassSchema(); // instead of GeneratedType.SCHEMA$
GeneratedType.CODER.createDecoder(new CustomSchemaStore()); // instead of
GeneratedType.createDecoder(new CustomSchemaStore());
{code}
---------------
this does not include external interface.
> Schema polymorphism
> -------------------
>
> Key: AVRO-2918
> URL: https://issues.apache.org/jira/browse/AVRO-2918
> Project: Apache Avro
> Issue Type: New Feature
> Components: logical types, misc, spec
> Reporter: Jonathan Rapoport
> Assignee: Christophe Le Saec
> Priority: Critical
> Labels: features, pull-request-available
> Original Estimate: 96h
> Time Spent: 20m
> Remaining Estimate: 95h 40m
>
> Include the option to use named types as base types for a new schema. Allow
> for MRO generation. Field inheritance.
> The benefits of this approach include:
> * Defining a schema as validation for a certain wire, and so allowing the
> receiver to be certain of the structure of the data (this works today).
> However, defining an extension of this schema, or certain schemas which can
> be normalized to the original schema, but contain additional information,
> will not allow it to be sent over the same wire.
> * Backwards compatibility through inheritance - you never break the old
> schema, thus allowing a long integration period, with no need to recode all
> processes familiar with the schema. The new schema will simply inherit the
> old one, and only add information.
> * Allow for full data control through polymorphism, and the ability to
> replace structures within any supported language.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
