[
https://issues.apache.org/jira/browse/AVRO-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778511#action_12778511
]
Jeff Hammerbacher commented on AVRO-153:
----------------------------------------
Pulling in some comments from Doug on the dev mailing list about the expanded
scope for this issue:
{quote}
The spec should be updated. Schemas can specify a namespace. If they're
nested in another schema or protocol then the namespace defaults to the
namespace of the containing schema or protocol.
Another thing that should be updated in the spec is that a name can be
namespace-qualified. This is useful to refer to types in a different
namespace, e.g., a field like:
{"name": "foo", "type": "org.apache.hadoop.util.MD5"}
This is related to https://issues.apache.org/jira/browse/AVRO-153.
The spec currently prohibits dots in identifiers. We should clarify that dots
are permitted in namespaces, and that, if present in a name, the last dot
separates the name from the namespace.
{quote}
> Naming conventions for avro records and protocols
> -------------------------------------------------
>
> Key: AVRO-153
> URL: https://issues.apache.org/jira/browse/AVRO-153
> Project: Avro
> Issue Type: Improvement
> Components: spec
> Reporter: Philip Zeyliger
>
> It would be nice to add a few paragraphs to the spec with suggested naming
> conventions. I'm ambivalent as to what they actually are, but while the
> paint hasn't fully settled, it might be nice to lead the project in one
> direction or another.
> Any thoughts on what the best style here is?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
