avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Cui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1836) avro schema compatibility checking does not work for records.
Date Mon, 02 May 2016 17:43:12 GMT

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

Yan Cui commented on AVRO-1836:

Hi Ryan, thanks for your reply!
It solves our problem. Does it make sense to support just one parser (instead of two)?
Without your help, it 's really easy to use it wrongly, although I do not have 
the data of how many people make exactly the same mistake.  

> avro schema compatibility checking does not work for records.
> -------------------------------------------------------------
>                 Key: AVRO-1836
>                 URL: https://issues.apache.org/jira/browse/AVRO-1836
>             Project: Avro
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>            Reporter: Yan Cui
>            Priority: Blocker
> Hi Guys, 
> We found a problem on avro 1.8.0 when calling avro's compatibility checking. 
> Specifically, we used the function checkReaderWriterCompatibility, 
> it works with no problem when we provides simple schema, like oldschema={"type":"int"}
schema={"type":"long"}, but when we use complicated schema, like 
> oldschema={"type":"record","name":"twitter","fields":[{"name":"username","type":"string"}]}
> schema={"type":"record","name":"twitter","fields":[{"name":"username","type":"string"}]}
> it reports that record name(twitter in this case) cannot be redefined. 
> When one rename the second schema, it told me the two schema are not compatible. Actually,
for the completed case, oldschema and schema are exactly the same, the output is expected
to be compatible.
> Do you guys have any ideas about this?
> Thanks, Yan

This message was sent by Atlassian JIRA

View raw message