[
https://issues.apache.org/jira/browse/AVRO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728816#action_12728816
]
Doug Cutting commented on AVRO-30:
----------------------------------
> we should eliminate namespaces for schemas but keep them for protocols
So it would then be illegal to use a given name twice in either a schema or a
protocol, right? This would make assembling protocols and schemas by file
inclusion from datastructure libraries tricky, since different libraries might
use the same name for different things.
Also, we'd like runtimes to be able to match Avro schemas with defined
datastructures in a language. E.g., in Java it might be nice if a schema whose
name was "Path" and whose namespace was "org.apache.hadoop.fs" could be
represented as an org.apache.hadoop.fs.Path instance. Tracking the namespace
of schemas enables this.
> 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
>
> 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.
