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

ASF subversion and git services commented on AVRO-1819:
-------------------------------------------------------

Commit 4c1463cba1bc268c2ccf2a506d27e6ee84030316 in avro's branch 
refs/heads/master from k.usachev
[ https://git-wip-us.apache.org/repos/asf?p=avro.git;h=4c1463c ]

AVRO-1819, AVRO-1820: Java: Add aliases, custom properties to Protocol. 
Contributed by Konstantin Usachev.


> 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
>
> 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.4#6332)

Reply via email to