You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@avro.apache.org by cu...@apache.org on 2012/02/09 22:38:14 UTC
svn commit: r1242540 - in /avro/trunk: CHANGES.txt
doc/src/content/xdocs/spec.xml
Author: cutting
Date: Thu Feb 9 21:38:13 2012
New Revision: 1242540
URL: http://svn.apache.org/viewvc?rev=1242540&view=rev
Log:
AVRO-1021. Clarify some naming issues in the specification. Contributed by Raymie Stata.
Modified:
avro/trunk/CHANGES.txt
avro/trunk/doc/src/content/xdocs/spec.xml
Modified: avro/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/avro/trunk/CHANGES.txt?rev=1242540&r1=1242539&r2=1242540&view=diff
==============================================================================
--- avro/trunk/CHANGES.txt (original)
+++ avro/trunk/CHANGES.txt Thu Feb 9 21:38:13 2012
@@ -76,6 +76,9 @@ Avro 1.6.2 (unreleased)
AVRO-1015. Support for C++ build using Micrsoft Visual Studio on Windows.
(thiru)
+ AVRO-1021. Clarify some naming issues in the specification.
+ (Raymie Stata via cutting)
+
BUG FIXES
AVRO-962. Java: Fix Maven plugin to support string type override.
Modified: avro/trunk/doc/src/content/xdocs/spec.xml
URL: http://svn.apache.org/viewvc/avro/trunk/doc/src/content/xdocs/spec.xml?rev=1242540&r1=1242539&r2=1242540&view=diff
==============================================================================
--- avro/trunk/doc/src/content/xdocs/spec.xml (original)
+++ avro/trunk/doc/src/content/xdocs/spec.xml Thu Feb 9 21:38:13 2012
@@ -252,7 +252,9 @@
<li>start with <code>[A-Za-z_]</code></li>
<li>subsequently contain only <code>[A-Za-z0-9_]</code></li>
</ul>
- <p>A namespace is a dot-separated sequence of such names.</p>
+ <p>A namespace is a dot-separated sequence of such names.
+ Equality of names (including field names and enum symbols)
+ as well as fullnames is case-sensitive.</p>
<p>In record, enum and fixed definitions, the fullname is
determined in one of the following ways:</p>
<ul>
@@ -278,9 +280,14 @@
they do not contain a dot, the namespace is the namespace of
the enclosing definition.</p>
<p>Primitive type names have no namespace and their names may
- not be defined in any namespace. A schema may only contain
- multiple definitions of a fullname if the definitions are
- equivalent.</p>
+ not be defined in any namespace.</p>
+ <p> 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 <code>types</code> attribute of
+ a protocol is always deemed to come "before" the
+ <code>messages</code> attribute.)
+ </p>
</section>
<section>