avro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cutt...@apache.org
Subject svn commit: r1588497 - in /avro/trunk: CHANGES.txt doc/src/content/xdocs/spec.xml
Date Fri, 18 Apr 2014 15:45:51 GMT
Author: cutting
Date: Fri Apr 18 15:45:51 2014
New Revision: 1588497

URL: http://svn.apache.org/r1588497
AVRO-1402. Add optional subtypes to specification.  Contributed by tomwhite & Ryan Blue.


Modified: avro/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/avro/trunk/CHANGES.txt?rev=1588497&r1=1588496&r2=1588497&view=diff
--- avro/trunk/CHANGES.txt (original)
+++ avro/trunk/CHANGES.txt Fri Apr 18 15:45:51 2014
@@ -11,6 +11,10 @@ Trunk (not yet released)
     AVRO-1471. Java: Permit writing generated code in different
     character encodings. (Eugene Mustaphin via cutting)
+    AVRO-1402. Add optional subtypes to specification, initially
+    including a subtype of bytes and fixed for decimal values.
+    (tomwhite & Ryan Blue via cutting)
     AVRO-1455. Deep copy does not need to create new instances for primitives.

Modified: avro/trunk/doc/src/content/xdocs/spec.xml
URL: http://svn.apache.org/viewvc/avro/trunk/doc/src/content/xdocs/spec.xml?rev=1588497&r1=1588496&r2=1588497&view=diff
--- avro/trunk/doc/src/content/xdocs/spec.xml (original)
+++ avro/trunk/doc/src/content/xdocs/spec.xml Fri Apr 18 15:45:51 2014
@@ -1336,6 +1336,73 @@ void initFPTable() {
+    <section>
+      <title>Logical Types</title>
+      <p>A logical type is an Avro primitive or complex type with extra attributes
+        represent a derived type. The attribute <code>logicalType</code> must
+        always be present for a logical type, and is a string with the name of one of
+        the logical types listed later in this section. Other attributes may be defined
+        for particular logical types.</p>
+      <p>A logical type is always serialized using its underlying Avro type so
+        that values are encoded in exactly the same way as the equivalent Avro
+        type that does not have a <code>logicalType</code> attribute. Language
+        implementations may choose to represent logical types with an
+        appropriate native type, although this is not required.</p>
+      <p>Language implementations must ignore unknown logical types when
+        reading, and should use the underlying Avro type. If a logical type is
+        invalid, for example a decimal with scale greater than its precision,
+        then implementations should ignore the logical type and use the
+        underlying Avro type.</p>
+      <section>
+        <title>Decimal</title>
+        <p>The <code>decimal</code> logical type represents an arbitrary-precision
+          decimal number of the form <em>unscaled &#215; 10<sup>-scale</sup></em>.</p>
+        <p>A <code>decimal</code> logical type annotates Avro
+          <code>bytes</code> or <code>fixed</code> types. The byte
array must
+          contain the two's-complement representation of the unscaled integer
+          value in big-endian byte order. The scale is fixed, and is specified
+          using an attribute.</p>
+        <p>The following attributes are supported:</p>
+        <ul>
+          <li><code>scale</code>, a JSON integer representing the scale
+            (optional). If not specified the scale is 0.</li>
+          <li><code>precision</code>, a JSON integer representing the (maximum)
+            precision of decimals stored in this type (required).</li>
+        </ul>
+        <p>For example, the following schema represents decimal numbers with a
+          maximum precision of 4 and a scale of 2:</p>
+        <source>
+  "type": "bytes",
+  "logicalType": "decimal",
+  "precision": 4,
+  "scale": 2
+        <p>Precision must be a positive integer greater than zero. If the
+          underlying type is a <code>fixed</code>, then the precision is
+          limited by its size. An array of length <code>n</code> can store at
+          most <em>floor(log_10(2<sup>8 &#215; n - 1</sup> - 1))</em>
+          base-10 digits of precision.</p>
+        <p>Scale must be zero or a positive integer less than or equal to the
+          precision.</p>
+        <p>For the purposes of schema resolution, two schemas that are
+          <code>decimal</code> logical types <em>match</em> if their
scales and
+          precisions match.</p>
+      </section>
+    </section>
   <p><em>Apache Avro, Avro, Apache, and the Avro and Apache logos are
    trademarks of The Apache Software Foundation.</em></p>

View raw message