You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/10 04:48:41 UTC

[jira] [Commented] (AVRO-1819) org.apache.avro.Protocol.parseMessage doesn't respect request field's aliases

    [ https://issues.apache.org/jira/browse/AVRO-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860699#comment-15860699 ] 

ASF GitHub Bot commented on AVRO-1819:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/avro/pull/83


> 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
(v6.3.15#6346)