You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Gabor Szadovszky (JIRA)" <ji...@apache.org> on 2017/09/07 11:56:00 UTC
[jira] [Updated] (AVRO-1933) SchemaCompatibility class could be
more user-friendly about incompatibilities
[ https://issues.apache.org/jira/browse/AVRO-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Szadovszky updated AVRO-1933:
-----------------------------------
Hadoop Flags: Incompatible change
Release Note: SchemaCompatibility returns the more detailed object SchemaCompatibilityResult instead of the simple enum SchemaCompatibilityType.
> 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)