[
https://issues.apache.org/jira/browse/AVRO-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143200#comment-16143200
]
Felix GV commented on AVRO-1340:
--------------------------------
I think we're on the same page...
Going from no fallback to a fallback is probably acceptable. But going from a
fallback to another fallback, or from a fallback to no fallback is probably
wrong...
Another edge case to consider, however, is if removing enum values is
acceptable. Is it only acceptable within enums that have a fallback drfined?
What if I try to remove an enum value that is also selected as the fallback, is
that prohibited in that case?
There are lots of edge cases to define, which is why I'm in favor of doing just
a fallback and doing it right, than to also provide generic enum aliases and
introducing even more edge case complexity...
I'd be curious to hear the others' opinions on these latest proposals.
> use default to allow old readers to specify default enum value when
> encountering new enum symbols
> -------------------------------------------------------------------------------------------------
>
> Key: AVRO-1340
> URL: https://issues.apache.org/jira/browse/AVRO-1340
> Project: Avro
> Issue Type: Improvement
> Components: spec
> Environment: N/A
> Reporter: Jim Donofrio
> Priority: Minor
>
> The schema resolution page says:
> > if both are enums:
> > if the writer's symbol is not present in the reader's enum, then an
> error is signalled.
> This makes it difficult to use enum's because you can never add a enum value
> and keep old reader's compatible. Why not use the default option to refer to
> one of enum values so that when a old reader encounters a enum ordinal it
> does not recognize, it can default to the optional schema provided one. If
> the old schema does not provide a default then the older reader can continue
> to fail as it does today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
