avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Rosenstrauch (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-601) Enhance schema parser to allow arbitrary properties to be defined on a record field
Date Mon, 02 Aug 2010 19:41:17 GMT

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

David Rosenstrauch commented on AVRO-601:

My apologies - I've been swamped with work, and haven't had a chance to review/test the patch.
 Will try to test it if I have time, but if I can't get to it in a timely fashion, and you're
convinced it works and fixes the bug, then by all means please proceed to release it.  If
the fix provides the functionality/API that I detailed in my first comment on this ticket
(or something close to it) I'm sure I'll be happy.

Thanks much for the fix (and the quick turn-around) on this!

> Enhance schema parser to allow arbitrary properties to be defined on a record field
> -----------------------------------------------------------------------------------
>                 Key: AVRO-601
>                 URL: https://issues.apache.org/jira/browse/AVRO-601
>             Project: Avro
>          Issue Type: Improvement
>          Components: java, spec
>         Environment: All
>            Reporter: David Rosenstrauch
>            Assignee: Doug Cutting
>            Priority: Minor
>             Fix For: 1.4.0
>         Attachments: AVRO-601.patch, AVRO-601.patch, AVRO-601.patch, AVRO-601.patch
> It's currently not possible to add an arbitrary property on a record field.  e.g., in
the following example, although the schema parses fine, the "alias" property gets thrown away:
> {
>     "name": "KVPair",
>     "type": "record",
>     "fields" : [
>         {"name": "key", "type": "int", "alias": "EventTime"},
>         {"name": "values", "type": "bytes"}
>     ]
> }
> I had read the Avro spec and thought this was actually allowed ("Attributes not defined
in this document are permitted as metadata, but must not affect the format of serialized data.")
but it appears that such additional properties are only allowed at the schema level, not at
the field level too.
> This would be a really useful feature to have, as it would allow the user to define meta-data
on a field.  Currently the only other way to achieve the same behavior would be to do some
kind of hack using the field's "doc" attribute, which would be rather ugly. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message