You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2009/12/01 21:09:20 UTC

[jira] Commented: (AVRO-242) add support for per-schema metadata

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

Doug Cutting commented on AVRO-242:
-----------------------------------

My thinking is that the Java API would initially only get/set string-based values.  It should probably throw an exception when you attempt to read a string that has a non-string, non-empty value.

> add support for per-schema metadata
> -----------------------------------
>
>                 Key: AVRO-242
>                 URL: https://issues.apache.org/jira/browse/AVRO-242
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.3.0
>
>
> The Avro specification permits schema json to contain other property names to be used besides those listed in the specification.  I propose adding support to Java for getting and setting these.

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