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] [Commented] (AVRO-1157) Idl tool - parse properties as plain String OR expose the property as Json
Date Fri, 14 Sep 2012 17:52:07 GMT

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

Doug Cutting commented on AVRO-1157:
------------------------------------

> My point is the current behaviour is inconsistent and rather odd...

I think of it as consistent but limited.  The syntax for annotations is consistently JSon
but the implementation is limited in that it currently ignores annotations that are not strings,
or, in the case of aliases, arrays of strings.  It's designed so that we can add support for
full Json annotations without breaking anything.  If we made the quick fix discussed above
then we'd have a harder time subsequently adding real support for Json annotations without
breaking applications.

I agree that adding full support for Json annotations to Protocol, Schema and Field would
be an improvement.  I'll try to create a patch that implements this when I have a chance and
if someone else doesn't do so first.
                
> 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