[
https://issues.apache.org/jira/browse/AVRO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709462#action_12709462
]
Doug Cutting commented on AVRO-30:
----------------------------------
> I have just moved the protocol name under "messages" .
That would not permit a message named "protocol". Perhaps instead we could
make the messages and protocol fields optional, so that a .avro file might just
contain namespace and types.
We might also consider a ".avroh" format that's suitable for textual inclusion,
so that one might have:
{code}
{"namespace": "org.apache.avro.test",
"types": [
#include mytypes.avroh
...
}
{code}
I'd rather avoid having explicit support for include in the JSON data, since we
generally want schema and protocol JSON to include the transitive closure, so
that they're portable, easy to persist, and standalone.
> name lookup should consider namespace
> -------------------------------------
>
> Key: AVRO-30
> URL: https://issues.apache.org/jira/browse/AVRO-30
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Doug Cutting
> Fix For: 1.0
>
>
> When a record schema is referred to by name, Avro will currently return any
> known record definition with that name, regardless of its namespace.
> Instead, unqualified references should refer to names in the current
> namespace, and namespace-qualfied names should look for a record in the given
> namespace.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
