avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chunfy.Tseng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1819) org.apache.avro.Protocol.parseMessage doesn't respect request field's aliases
Date Thu, 07 Jul 2016 00:48:11 GMT

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

Chunfy.Tseng commented on AVRO-1819:

When using RPC, the client can use such as httpclient similar tools or use postman plug-in
directly send? If you can then send the?

> 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