[jira] [Updated] (AVRO-1933) SchemaCompatibility class could be more user-friendly about incompatibilities

["Anders Sundelin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AVRO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anders Sundelin updated AVRO-1933:
----------------------------------
             Assignee: Anders Sundelin
    Affects Version/s: 1.7.7
               Status: Patch Available  (was: Open)

Two patches is attached, choose one, depending on whether AVRO-1931 is in the baseline or not

> 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.8.1, 1.7.7
>         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)