You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by dm...@apache.org on 2011/10/12 01:16:10 UTC
svn commit: r1182139 - in /hbase/trunk/src/docbkx: book.xml ops_mgt.xml
Author: dmeil
Date: Tue Oct 11 23:16:10 2011
New Revision: 1182139
URL: http://svn.apache.org/viewvc?rev=1182139&view=rev
Log:
HBASE-4576 book.xml,ops_mgt.xml - moved cluster repl into OpsMgt chapter.
Modified:
hbase/trunk/src/docbkx/book.xml
hbase/trunk/src/docbkx/ops_mgt.xml
Modified: hbase/trunk/src/docbkx/book.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/book.xml?rev=1182139&r1=1182138&r2=1182139&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/book.xml (original)
+++ hbase/trunk/src/docbkx/book.xml Tue Oct 11 23:16:10 2011
@@ -602,14 +602,14 @@ admin.enableTable(table);
"a lot" of versions of a row to be retained (e.g., where it is significantly above the HBase default of 3 max versions). The
rows-approach would require storing a timstamp in some portion of the rowkey so that they would not overwite with each successive update.
</para>
- <para>Winner: Rows (generally speaking).
+ <para>Preference: Rows (generally speaking).
</para>
</section>
<section xml:id="schema.smackdown.rowscols"><title>Rows vs. Columns</title>
<para>Another common question is whether one should prefer rows or columns. The context is typically in extreme cases of wide
tables, such as having 1 row with 1 million attributes, or 1 million rows with 1 columns apiece.
</para>
- <para>Winner: Rows (generally speaking). To be clear, this guideline is in the context is in extremely wide cases, not in the
+ <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.
</para>
</section>
@@ -681,12 +681,6 @@ admin.enableTable(table);
</section>
</chapter>
- <chapter xml:id="cluster_replication">
- <title>Cluster Replication</title>
- <para>See <link xlink:href="http://hbase.apache.org/replication.html">Cluster Replication</link>.
- </para>
- </chapter>
-
<chapter xml:id="datamodel">
<title>Data Model</title>
<para>In short, applications store data into an HBase table.
Modified: hbase/trunk/src/docbkx/ops_mgt.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/ops_mgt.xml?rev=1182139&r1=1182138&r2=1182139&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/ops_mgt.xml (original)
+++ hbase/trunk/src/docbkx/ops_mgt.xml Tue Oct 11 23:16:10 2011
@@ -251,6 +251,13 @@ false
<para>TODO
</para>
</section>
+
+ <section xml:id="cluster_replication">
+ <title>Cluster Replication</title>
+ <para>See <link xlink:href="http://hbase.apache.org/replication.html">Cluster Replication</link>.
+ </para>
+ </section>
+
<section xml:id="ops.backup">
<title >HBase Backup</title>
<para>There are two broad strategies for performing HBase backups: backing up with a full cluster shutdown, and backing up on a live cluster.