[
https://issues.apache.org/jira/browse/AVRO-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822556#comment-16822556
]
ASF subversion and git services commented on AVRO-2275:
-------------------------------------------------------
Commit ea61af812478af7e6922b83e0818bf06b91c0052 in avro's branch
refs/heads/master from rstata
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=ea61af8 ]
AVRO-2275 Some name cleanup, plus changes to make it easier to utilize
Resolver.Action trees.
> Refactor schema-resolution code from grammar-generation
> -------------------------------------------------------
>
> Key: AVRO-2275
> URL: https://issues.apache.org/jira/browse/AVRO-2275
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
> Reporter: Raymie Stata
> Assignee: Raymie Stata
> Priority: Major
>
> In my own work to extend AVRO-2090, and also in AVRO-2247, an alternative
> approach optimizing decoders, we were forced to re-implement Schema
> resolution logic because it's currently embedded deeply in
> ResolvingGrammarGenerator. However, in the past the Avro community found it
> hard to maintain multiple implementations of the schema resolution code, as
> it is tedious and error-prone code.
> In this JIRA we've refactored the resolution code into a new class called
> Resolver, and have rewritten ResolvingGrammarGenerator to be a client of this
> class. This rewrite passes the full regression suite, including bug-for-bug
> compatibility with a few questionable resolutions rules, such as the "soft
> matching" rule for record in unions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
