hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dm...@apache.org
Subject svn commit: r1414725 - /hbase/trunk/src/docbkx/book.xml
Date Wed, 28 Nov 2012 14:27:45 GMT
Author: dmeil
Date: Wed Nov 28 14:27:44 2012
New Revision: 1414725

URL: http://svn.apache.org/viewvc?rev=1414725&view=rev
hbase-7228.  book.xml.  Schema Design - adding entry for "rows as columns"


Modified: hbase/trunk/src/docbkx/book.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/book.xml?rev=1414725&r1=1414724&r2=1414725&view=diff
--- hbase/trunk/src/docbkx/book.xml (original)
+++ hbase/trunk/src/docbkx/book.xml Wed Nov 28 14:27:44 2012
@@ -942,9 +942,20 @@ System.out.println("md5 digest as string
       tables, such as having 1 row with 1 million attributes, or 1 million rows with 1 columns
       <para>Preference:  Rows (generally speaking).  To be clear, this guideline is
in the context is in extremely wide cases, not in the
-      standard use-case where one needs to store a few dozen or hundred columns.
+      standard use-case where one needs to store a few dozen or hundred columns.  But there
is also a middle path between these two
+      options, and that is "Rows as Columns." 
+    <section xml:id="schema.smackdown.rowsascols"><title>Rows as Columns</title>
+      <para>The middle path between Rows vs. Columns is packing data that would be
a separate row into columns, for certain rows.
+      OpenTSDB is the best example of this case where a single row represents a defined time-range,
and then discrete events are treated as
+      columns.  This approach is often more complex, and may require the additional complexity
of re-writing your data, but has the 
+      advantage of being I/O efficient.  For an overview of this approach, see 
+      <link xlink:href="http://www.cloudera.com/content/cloudera/en/resources/library/hbasecon/video-hbasecon-2012-lessons-learned-from-opentsdb.html">Lessons
Learned from OpenTSDB</link> 
+      from HBaseCon2012.
+      </para>
+    </section>
   <section xml:id="schema.ops"><title>Operational and Performance Configuration
     <para>See the Performance section <xref linkend="perf.schema"/> for more
information operational and performance

View raw message