[
https://issues.apache.org/jira/browse/AVRO-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203999#comment-13203999
]
Raymie Stata commented on AVRO-1021:
------------------------------------
{quote} 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? {quote}
Good catch. I looked at Schemas and verified that types appear in arrays, but
not protocols. What if I changed my older text to the following: "A schema or
protocol may not contain multiple definitions of a fullname. Further, a name
must be defined before it is used ("before" in the depth-first, left-to-right
traversal of the JSON parse tree, where the {{types}} attribute of a protocol
is always deemed to come "before" the {{messages}} attribute.)" A bit windy,
but precise.
{quote}It would sure be nice if there were a few shared folders that every
language tested schemas and protocols against.{quote}
The test-suite I'm writing for AVRO-1006 will include a file of test cases in
{{src/test/resources}} that could be the basis of what you're talking about
here. I'll get that posted soon, you can look at it and see what more would
need to be done.
> 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
