New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Schema resolution: conform more closely with Avro spec #132

Closed

2 of 3 tasks

bplommer opened this issue Jan 15, 2020 · 1 comment

Closed

2 of 3 tasks

Schema resolution: conform more closely with Avro spec #132

bplommer opened this issue Jan 15, 2020 · 1 comment

Member

bplommer commented Jan 15, 2020 •

edited by vlovgr

Loading

Writer schema validation is currently more strict than mandated by the Avro spec (https://avro.apache.org/docs/1.9.1/spec.html#Schema+Resolution), meaning schema evolutions that should be allowed are not.

~~Support promotion between different schema types, e.g. from int writer schema to long reader schema (Schema resolution: allow type promotion #134)~~
~~Match named schema based on name rather than fullname (Remove name validation from codecs, match unions based on name rather than fullname #136)~~
Allow matching named schema based on aliases

We may not need to handle schema name matching ourselves at all, since it's already done by the underlying Avro library.

The text was updated successfully, but these errors were encountered:

bplommer mentioned this issue

Schema resolution: allow type promotion #134

Closed

vlovgr mentioned this issue

Add support for aliases #142

Open

Contributor

vlovgr commented Jan 20, 2020

Moved alias support to #142.

vlovgr closed this as completed

vlovgr mentioned this issue

Union codecs do not match by namespace #385

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment