You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/07/08 16:28:06 UTC

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

    [ https://issues.apache.org/jira/browse/AVRO-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618684#comment-14618684 ] 

ASF subversion and git services commented on AVRO-1645:
-------------------------------------------------------

Commit 1689884 from tomwhite@apache.org in branch 'avro/trunk'
[ https://svn.apache.org/r1689884 ]

AVRO-1645. Ruby: Improved handling of missing named types. Contributed by Daniel Schierbeck.

> 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
>             Fix For: 1.7.8, 1.8.0
>
>         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)