avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satish Duggana (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AVRO-1933) SchemaCompatibility class could be more user-friendly about incompatibilities
Date Wed, 01 Mar 2017 04:00:48 GMT

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

Satish Duggana edited comment on AVRO-1933 at 3/1/17 3:59 AM:
--------------------------------------------------------------

[~cutting] [~rdblue] It is nice to have this as it gives more insight into what is wrong with
the schema when it is checked for compatibility with another schema. 

AVRO-2003 adds location details about the incompatible elements. 

[~epkanol] I guess you need to raise PR for this JIRA. 


was (Author: satish.duggana):
[~cutting] [~rdblue] It is nice to have this as it gives more insight into what is wrong with
the schema when it is checked for compatibility with another schema. 

[~epkanol] I guess you need to raise PR for this JIRA. 

> SchemaCompatibility class could be more user-friendly about incompatibilities
> -----------------------------------------------------------------------------
>
>                 Key: AVRO-1933
>                 URL: https://issues.apache.org/jira/browse/AVRO-1933
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.7.7, 1.8.1
>         Environment: Any Java env
>            Reporter: Anders Sundelin
>            Assignee: Anders Sundelin
>            Priority: Minor
>             Fix For: 1.9.0
>
>         Attachments: AVRO-1933-compatible-with-AVRO-1931.patch, AVRO-1933.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Today, the class SchemaCompatibility reports incompatibilities with quite little detail.
The whole reader and the whole writer schema is listed, and no particular detail about what
was incompatible.
> The attached patch fixes this, introducing a new enum (SchemaIncompatibilityType), and
more specific sub-schemas that were incompatible.
> The old, overall picture, is still there - the new compatibility state is encapsulated
in the SchemaCompatibilityDetails class.
> Lots of test cases have been added, and there has been refactoring done in the TestSchemaCompatibility
and other test classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message