[
https://issues.apache.org/jira/browse/AVRO-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797873#action_12797873
]
Jeff Hammerbacher commented on AVRO-75:
---------------------------------------
bq. I was under the impression that you were not allowed to read the schema
record(a=string) with the schema record(b=string), i.e., that this would throw
an exception when the schemas were being reconciled.
That's what we're discussing here. Currently, two record schemas are assumed to
"match" if they have the same name, regardless of fields. For the two record
schemas you specify, if they had the same name, we'd be in the first case I
mention above. According to the spec, the current behavior is that "the field's
value is unset". We're trying to clarify what "unset" means.
> Clarify resolution for enums (and fix code)
> -------------------------------------------
>
> Key: AVRO-75
> URL: https://issues.apache.org/jira/browse/AVRO-75
> Project: Avro
> Issue Type: Bug
> Components: spec
> Reporter: Raymie Stata
> Assignee: Doug Cutting
> Fix For: 1.3.0
>
>
> The current resolution rule for enum's says: "if the writer's symbol is not
> present in the reader's enum, then the enum value is unset." This is the
> only place the word "unset" is used in the doc, it's not clear what you mean.
> The code seems to be inconsistent: GenericDatumReader will happily return a
> symbol the reader doesn't understand; ReflectDatumReader will probably throw
> a class-not-found exception; ResolvingDecoder throws an error.
> I propose that we declare this case an error, i.e., rewrite the spec to "if
> the writer's symbol is not listed in the reader's enum, an error is
> signaled." GenericDatumReader should be updated to throw an error in this
> case.
> If we decide to stick with the "unset" language, we need to define what
> "unset" means (and, if necessary, update ReflectDatumReader and
> ResolvingDecoder).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
