avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-258) Higher-level language for authoring schemata
Date Mon, 21 Dec 2009 03:00:18 GMT

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

Todd Lipcon commented on AVRO-258:
----------------------------------

Thanks for the input, guys.

bq. We could make the properties, key-value: string name sort=ignore future=property

I'm not a huge fan of this because it makes user-properties intermix with language constructors
in a non-clearly-defined way. But I don't feel that strongly - anyone else have some opinions?

bq. The only addition I'd like to add to the grammar is to support optional fields in records

Definitely +1. I was planning on using the keyword "nullable" instead of "optional" since
to me "optional" seems to indicate a ternary state possibility (ie unset, set to null, and
set to something else). But in general I like that kind of syntactic sugar.

> Higher-level language for authoring schemata
> --------------------------------------------
>
>                 Key: AVRO-258
>                 URL: https://issues.apache.org/jira/browse/AVRO-258
>             Project: Avro
>          Issue Type: New Feature
>          Components: spec
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: AVRO-258.txt, simple-genned.avpr, simple.avpr
>
>
> Early users of Avro have noted that authoring schemas and especially protocols in JSON
feels unnatural. This JIRA is to work on a higher-level language that feels more like defining
interfaces and classes in Java/C/etc.

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


Mime
View raw message