avro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From marti...@apache.org
Subject svn commit: r1724128 - in /avro/branches/branch-1.8: CHANGES.txt doc/src/content/xdocs/spec.xml
Date Mon, 11 Jan 2016 21:00:25 GMT
Author: martinkl
Date: Mon Jan 11 21:00:24 2016
New Revision: 1724128

URL: http://svn.apache.org/viewvc?rev=1724128&view=rev
Log:
AVRO-1725. Docs: clarify restrictions on enum symbols.

Modified:
    avro/branches/branch-1.8/CHANGES.txt
    avro/branches/branch-1.8/doc/src/content/xdocs/spec.xml

Modified: avro/branches/branch-1.8/CHANGES.txt
URL: http://svn.apache.org/viewvc/avro/branches/branch-1.8/CHANGES.txt?rev=1724128&r1=1724127&r2=1724128&view=diff
==============================================================================
--- avro/branches/branch-1.8/CHANGES.txt (original)
+++ avro/branches/branch-1.8/CHANGES.txt Mon Jan 11 21:00:24 2016
@@ -242,6 +242,8 @@ Avro 1.8.0 (15 December 2015)
     AVRO-1772. Ruby: load error in rubygem when loading schema normalization.
     (blue and martinkl via tomwhite)
 
+    AVRO-1725. Docs: clarify restrictions on enum symbols. (martinkl)
+
 Avro 1.7.7 (23 July 2014)
 
   NEW FEATURES

Modified: avro/branches/branch-1.8/doc/src/content/xdocs/spec.xml
URL: http://svn.apache.org/viewvc/avro/branches/branch-1.8/doc/src/content/xdocs/spec.xml?rev=1724128&r1=1724127&r2=1724128&view=diff
==============================================================================
--- avro/branches/branch-1.8/doc/src/content/xdocs/spec.xml (original)
+++ avro/branches/branch-1.8/doc/src/content/xdocs/spec.xml Mon Jan 11 21:00:24 2016
@@ -171,7 +171,9 @@
 	    user of this schema (optional).</li>
 	    <li><code>symbols</code>: a JSON array, listing symbols,
 	    as JSON strings (required).  All symbols in an enum must
-	    be unique; duplicates are prohibited.</li>
+	    be unique; duplicates are prohibited.  Every symbol must
+	    match the regular expression <code>[A-Za-z_][A-Za-z0-9_]*</code>
+	    (the same requirement as for <a href="#names">names</a>).</li>
 	  </ul>
 	  <p>For example, playing card suits might be defined with:</p>
 	  <source>
@@ -246,7 +248,7 @@
 
       </section> <!-- end complex types -->
 
-      <section>
+      <section id="names">
 	<title>Names</title>
         <p>Record, enums and fixed are named types.  Each has
           a <em>fullname</em> that is composed of two parts;



Mime
View raw message