[
https://issues.apache.org/jira/browse/AVRO-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452589#comment-16452589
]
Doug Cutting commented on AVRO-1340:
------------------------------------
Sorry, I misunderstood the question. The atsign notation should not work here.
For field defaults, attempting the atsign notation would result in an error
when it tries to set that schema property. (The compiler builds a schema then
generates Json from it.) We should similarly fix the enum schema API to
prohibit "default" as a settable property name, in Schema.java.
To minimize incompatiblity, I think we should create a list of reserved
property names for EnumSchema that adds "default" to SCHEMA_RESERVED.
> 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)
