[
https://issues.apache.org/jira/browse/AVRO-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793941#comment-13793941
]
graham sanderson commented on AVRO-1385:
----------------------------------------
I can see arguments both ways, but personally I think the current behavior is
reasonable. Assuming you are the one controlling your schema, I don't think the
intention is to avoid being surprised by a schema change. Removing a no longer
used enum value is good... choosing to change the data type of a numeric value
to a less precise type (with advanced warning that that is how Avro works) is
probably on your own head.
> Enum reader/writer resolution doesn't report errors
> ---------------------------------------------------
>
> Key: AVRO-1385
> URL: https://issues.apache.org/jira/browse/AVRO-1385
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.7.5
> Reporter: Christophe Taton
> Attachments:
> AVRO-1385.base=a56e7f13c4fa976b7926649b058665f42850a349.20131010-182234.patch
>
>
> According to the specification, when a reader enum does not contain all
> symbols from the writer enum, an error should be signaled.
> ResolvingGrammarGenerator fails to report such errors.
> In particular, mkEnumAdjust() silently maps unknown symbols of the writers
> with symbols named "No match for [writer symbol]".
> https://github.com/apache/avro/blob/trunk/lang/java/avro/src/main/java/org/apache/avro/io/parsing/ResolvingGrammarGenerator.java#L409
> Shouldn't this instead create an ErrorAction?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
