avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Blue (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AVRO-1819) org.apache.avro.Protocol.parseMessage doesn't respect request field's aliases
Date Wed, 20 Apr 2016 17:13:25 GMT

     [ https://issues.apache.org/jira/browse/AVRO-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ryan Blue resolved AVRO-1819.
       Resolution: Fixed
    Fix Version/s: 1.8.1

I committed this fix. Thanks for contributing, [~DrVirtual]!

> org.apache.avro.Protocol.parseMessage doesn't respect request field's aliases
> -----------------------------------------------------------------------------
>                 Key: AVRO-1819
>                 URL: https://issues.apache.org/jira/browse/AVRO-1819
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.9.0
>            Reporter: Konstantin Usachev
>            Assignee: Konstantin Usachev
>             Fix For: 1.8.1
> Avro specification (https://avro.apache.org/docs/1.8.0/spec.html#Aliases "Named types
and fields may have aliases") and Idl compiler supports aliases on request's fields. But org.apache.avro.Protocol.parseMessage
have a special code to parse request body (not the same as for an ordinary record) and during
field parsing we don't keep info about aliases. So it leads to lack of important functionality
supporting protocol refactoring with backward compatibility.

This message was sent by Atlassian JIRA

View raw message