avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AVRO-1157) Idl tool - parse properties as plain String OR expose the property as Json
Date Thu, 13 Sep 2012 17:50:08 GMT

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

Doug Cutting updated AVRO-1157:
-------------------------------

    Attachment: AVRO-1157.patch

Here's a patch that implements this.  However note how strange the addition to simple.avpr
looks.  If we really want to support complex Json annotations then we should really extend
the APIs of Protocol, Schema, and Field.

What's the motivating use case?  In the examples you provide above, why can't you simply use
something like, @EntityColumnFamily("test"), @ColumnId("id") and @ColumnName("name")?
                
> Idl tool - parse properties as plain String OR expose the property as Json
> --------------------------------------------------------------------------
>
>                 Key: AVRO-1157
>                 URL: https://issues.apache.org/jira/browse/AVRO-1157
>             Project: Avro
>          Issue Type: Improvement
>          Components: java, spec
>    Affects Versions: 1.7.1
>            Reporter: Cristian Opris
>            Priority: Minor
>         Attachments: AVRO-1157.patch
>
>
> The IDL Tool currently parses "annotations" as Json objects but only really supports
textual values.
> If one wants to have actual json annotations, they need to write json as an escaped json
string.
> Proposed solutions:
> - expose the property as Json if it's parsed as Json
> - OR  parse the property as a string

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message