[
https://issues.apache.org/jira/browse/AVRO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156871#comment-16156871
]
ASF subversion and git services commented on AVRO-1933:
-------------------------------------------------------
Commit db8ed216eaf13c8f3862eb31152185f0504c4467 in avro's branch
refs/heads/master from [~epkanol]
[ https://git-wip-us.apache.org/repos/asf?p=avro.git;h=db8ed21 ]
AVRO-1933: Add more specific error details to SchemaCompatibility class
Closes #200
Signed-off-by: Sriharsha Chintalapani <[email protected]>
Signed-off-by: Anna Szonyi <[email protected]>
Signed-off-by: Nandor Kollar <[email protected]>
Signed-off-by: Gabor Szadovszky <[email protected]>
> 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.4.14#64029)
