hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dm...@apache.org
Subject svn commit: r1244681 - /hbase/trunk/src/docbkx/book.xml
Date Wed, 15 Feb 2012 19:59:28 GMT
Author: dmeil
Date: Wed Feb 15 19:59:28 2012
New Revision: 1244681

URL: http://svn.apache.org/viewvc?rev=1244681&view=rev
Log:
hbase-5408.  book.xml, moved "column metadata" section to top-level in Data Model chapter.

Modified:
    hbase/trunk/src/docbkx/book.xml

Modified: hbase/trunk/src/docbkx/book.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/book.xml?rev=1244681&r1=1244680&r2=1244681&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/book.xml (original)
+++ hbase/trunk/src/docbkx/book.xml Wed Feb 15 19:59:28 2012
@@ -290,16 +290,6 @@ try {
         </para>
  
       </section>
-      <section xml:id="dm.column.metadata">
-        <title>Column Metadata</title>
-        <para>There is no store of column metadata outside of the internal KeyValue
instances for a ColumnFamily.
-        Thus, while HBase can support not only a wide number of columns per row, but a heterogenous
set of columns 
-        between rows, it is your responsibility to keep track of the column names.      
 
-        </para>
-        <para>The only way to get a complete set of columns that exist for a ColumnFamily
is to process all the rows. 
-       	For more information about how HBase stores data internally, see <xref linkend="keyvalue"
/>.
-	    </para>         
-      </section>
             
     </section>
 
@@ -537,6 +527,16 @@ htable.put(put);
         </section>
       </section>
     </section>
+    <section xml:id="dm.column.metadata">
+      <title>Column Metadata</title>
+      <para>There is no store of column metadata outside of the internal KeyValue instances
for a ColumnFamily.
+      Thus, while HBase can support not only a wide number of columns per row, but a heterogenous
set of columns 
+      between rows as well, it is your responsibility to keep track of the column names.
       
+      </para>
+      <para>The only way to get a complete set of columns that exist for a ColumnFamily
is to process all the rows. 
+      For more information about how HBase stores data internally, see <xref linkend="keyvalue"
/>.
+	  </para>         
+    </section>
     <section xml:id="joins"><title>Joins</title>
       <para>Whether HBase supports joins is a common question on the dist-list, and
there is a simple answer:  it doesn't,
       at not least in the way that RDBMS' support them (e.g., with equi-joins or outer-joins
in SQL).  As has been illustrated



Mime
View raw message