[
https://issues.apache.org/jira/browse/AVRO-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336659#comment-16336659
]
Felix GV commented on AVRO-1340:
--------------------------------
I'm glad to hear that we're nearing a conclusion to this (: !
I'll be honest: I have not kept up with the spreadsheets and nuances of the
past few posts.
I'd like to propose the following litmus test for the new design: Can one of
you pretend I'm an Avro user, and jot down a 30 second elevator pitch
explaining what would I need to specify in my schema to do enum evolution in
Avro?
If it is possible to distill the compatibility rules in 30 seconds, then I
think I would be onboard, no matter what it is (:
If it proves impossible, I might still be onboard, but it may turn out to be a
bittersweet resolution... API simplicity is very important.
Hopefully I'm not making unreasonable demands on you fine gentlemen.
-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
(v7.6.3#76005)
