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 subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/16 21:43:08 UTC

[jira] [Commented] (AVRO-1409) Accurate method for evaluating schema compatibility

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

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

Commit 1551341 from [~cutting] in branch 'avro/trunk'
[ https://svn.apache.org/r1551341 ]

AVRO-1409. Java: Add an API for testing schema compatibility.  Contributed by Christophe Taton.

> Accurate method for evaluating schema compatibility
> ---------------------------------------------------
>
>                 Key: AVRO-1409
>                 URL: https://issues.apache.org/jira/browse/AVRO-1409
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Christophe Taton
>            Assignee: Christophe Taton
>             Fix For: 1.7.6
>
>         Attachments: AVRO-1409.20131203-202608.diff
>
>
> Following AVRO-1385, it appears Avro's resolving decoder performs decode-time compatibility check, ie. per datum instance compatibility check, as opposed to per schema compatibility check.
> For our use-cases, we need to determine whether all datum instances of a particular writer schema will always succeed in being decoded using a given reader schema.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)