[
https://issues.apache.org/jira/browse/AVRO-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257352#comment-15257352
]
Felix GV commented on AVRO-1340:
--------------------------------
Hello,
Until this issue gets fixed, it seems to me like Avro enums are close to
useless, since there is no way to evolve them gracefully. Is there any interest
in fixing this?
[~zolyfarkas]'s suggestion probably makes sense, though I can imagine some
people may have different opinions.
In any case, until this is resolved, it would probably be safer to put a
warning in the Avro documentation stating that enums are not evolvable and
should thus be used only at the user's own risk.
-F
> 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.3.4#6332)
