[
https://issues.apache.org/jira/browse/AVRO-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371672#comment-15371672
]
Ryan Blue commented on AVRO-1878:
---------------------------------
Yeah, that's it. The test passes if I rename the record or add an alias for the
old name.
I think we should go ahead with this patch and make the resolver handle
renames. Why should the resolver require pre-processing the schemas that are
passed in to work correctly? It seems like this kind of resolution is not only
part of the resolver's contract, but also something we should keep to one place
in the code. For instance, union resolution has similar logic based on field
names.
> 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)
