[
https://issues.apache.org/jira/browse/AVRO-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792396#action_12792396
]
Todd Lipcon commented on AVRO-258:
----------------------------------
Other open questions:
- Should this support complex defaults? If so, do we end up essentially
embedding JSON inside the language? Eg:
{noformat}
record SomeOtherRecord {
TestRecord myfield = {
'name': 'bob',
'kind': 'FOO',
'hash': 0x1234234
}
}
{noformat}
or should it be something with less quoting? In the first iteration, I'll
probably just leave out non-literal defaults.
- How do we write nested non-reference-style records? For example, part of
interop.avsc might be written something like:
{noformat}
@namespace(org.apache.avro)
record Interop {
record Node {
string label;
array<Node> children;
} recordField;
}
{noformat}
but that looks a little bizarre to me. The other option is to force records to
be defined more like inner classes:
{noformat}
@namespace(org.apache.avro)
record Interop {
record Node {
string label;
array<Node> children;
}
Node recordField;
}
{noformat}
> 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
>
> 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.
