[
https://issues.apache.org/jira/browse/AVRO-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371239#comment-15371239
]
Doug Cutting commented on AVRO-1878:
------------------------------------
Ryan, I'm not sure what you think is missing. Aliases are implemented in
GenericDatumReader#read() when Schema#applyAliases() rewrites the writer's
schema, renaming things according to aliases in the reader's schema. The
resolver is then created using the rewritten schema. Alias processing is
handled by the rewrite. The resolver should thus not need to be aware of
aliases. Or am I missing something?
What is the use case you feel is handled incorrectly?
> ResolvingGrammarGenerator doesn't handle aliases
> ------------------------------------------------
>
> Key: AVRO-1878
> URL: https://issues.apache.org/jira/browse/AVRO-1878
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.8.1
> Reporter: Ryan Blue
> Assignee: Ryan Blue
> Fix For: 1.8.2
>
>
> While testing AVRO-1704, I tested schema evolution using an aliased field and
> found that the ResolvingGrammarGenerator doesn't support field aliases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
