[
https://issues.apache.org/jira/browse/AVRO-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203788#comment-13203788
]
Doug Cutting commented on AVRO-1021:
------------------------------------
> if there is an Avro Data File or old schema that used a name before defining
> it that currently works
I don't think any implementation currently supports use-before-define, does it?
A "left-to-right traversal" of JSON only makes sense for array elements. The
only schemas that include multiple types and traversal order matters are unions
and records, but these use JSON arrays, so left-to-right works. The types
array in a protocol definition could come textually after the messages, but the
types must be processed before the messages and in-order. Should we clarify
that too?
> Fix a few name-related imperfections in Avro spec
> -------------------------------------------------
>
> Key: AVRO-1021
> URL: https://issues.apache.org/jira/browse/AVRO-1021
> Project: Avro
> Issue Type: Bug
> Components: spec
> Reporter: Raymie Stata
> Assignee: Raymie Stata
> Priority: Minor
> Attachments: AVRO-1021.patch, AVRO-1021.patch
>
>
> Require names are defined before used; disallow multiple definitions of
> names; clarify that name-equality is case sensitive (for type names, field
> names, and enum symbols).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
