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-258) Higher-level language for authoring schemata
Date Thu, 31 Dec 2009 21:23:29 GMT

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

Doug Cutting commented on AVRO-258:
-----------------------------------

One more change, Todd: Schema.Names should not have been made public: it has no Javadoc, it
references other non-public classes, and otherwise clutters the core Javadoc with something
that few need to know about.  Perhaps, in a separate issue, we could consider moving a lot
of Schema.java's nested classes to an implementation package, that most users don't need to
see, but for now using Schema.Names didn't actually save you more than a couple of lines of
code, so I just removed its use and made it package-private again.

> 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
>             Fix For: 1.3.0
>
>         Attachments: avro-258.txt, avro-258.txt, AVRO-258.txt, genavro.pdf, 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