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

Todd Lipcon updated AVRO-258:
-----------------------------

    Attachment: simple-genned.avpr
                simple.avpr
                AVRO-258.txt

Here's a patch that shows what works so far. It does not include proper unit 
tests yet, but you can try it like so:

{noformat}
$ ant compile-java
$ java -cp build/lib/*:build/classes/ org.apache.avro.genavro.GenAvro < 
src/test/genavro/simple.avpr
{noformat}

I also attached input and output for a schema basically the same as the 
test/schemata/simple.avpr

Certainly more work to be done here, but I want to get feedback from the 
community before I spend the time to get it properly tested, documented, 
corner-cases worked out, etc. Most importantly, is this something people want? 
Does this style of syntax seem reasonable?

> 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.

Reply via email to