You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/07/07 16:46:05 UTC

[jira] [Updated] (AVRO-1645) Improved handling of missing named types

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

Sean Busbey updated AVRO-1645:
------------------------------
    Attachment: AVRO-1645.1.patch

Attaching patch from [github pr #26|https://github.com/apache/avro/pull/26], with commit message modified to match the contributor guide.

+1 (non-binding) patch looks good to me. It's backwards compatible, so could go into 1.7 and 1.8. It passes ruby tests.

> Improved handling of missing named types
> ----------------------------------------
>
>                 Key: AVRO-1645
>                 URL: https://issues.apache.org/jira/browse/AVRO-1645
>             Project: Avro
>          Issue Type: Improvement
>            Reporter: Daniel Schierbeck
>         Attachments: AVRO-1645.1.patch
>
>
> I've written a Ruby library that wraps the Avro Ruby library and provides a "registry" of schemas. The idea is to allow users to avoid repeating themselves by allowing inter-schema references using the type names. At runtime any missing type is resolved by loading the relevant schema from disk.
> This works great, but depends on parsing the error message from the Avro::SchemaParseError exception, extracting the name of the missing type. If there was a more specific subclass, e.g. Avro::MissingSchemaError, that provided an attribute with the name of the schema, my library would be a lot more robust. I'd rather not have everything break if you change the error message.
> I've added a PR here: https://github.com/apache/avro/pull/26
> Here's the project: https://github.com/dasch/avro_turf (still in development)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)