[ https://issues.apache.org/jira/browse/AVRO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568638#comment-15568638 ]
Anders Sundelin edited comment on AVRO-1933 at 10/12/16 2:56 PM: ----------------------------------------------------------------- Patch set adding more error details to SchemaCompatibility. Also includes part of AVRO-1931 (though not all tests therein) This patch is not compatible with changes done in AVRO-1931 - if you come that way, please use the other patch attached to this issue. Contact me if there is any issues. was (Author: epkanol): Patch set adding more error details to SchemaCompatibility. Also includes part of AVRO-1931 (though not all tests therein) Suggest to apply AVRO-1931 first, then this patch. Contact me if there is any issues. > 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 > Environment: Any Java env > Reporter: 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.4#6332)