Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-4576 book.xml,ops_mgt.xml - moved cluster repl into OpsMgt chapter. 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1182139 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Doug Meil 2011-10-11 23:16:10 +00:00
parent ed7605b892
commit c52469aad9
2 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/docbkx/book.xml
View File

@ -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 "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. 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>
<para>Winner: Rows (generally speaking). <para>Preference: Rows (generally speaking).
</para> </para>
</section> </section>
<section xml:id="schema.smackdown.rowscols"><title>Rows vs. Columns</title> <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 <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. tables, such as having 1 row with 1 million attributes, or 1 million rows with 1 columns apiece.
</para> </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. standard use-case where one needs to store a few dozen or hundred columns.
</para> </para>
</section> </section>
@ -681,12 +681,6 @@ admin.enableTable(table);
</section> </section>
</chapter> </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"> <chapter xml:id="datamodel">
<title>Data Model</title> <title>Data Model</title>
<para>In short, applications store data into an HBase table. <para>In short, applications store data into an HBase table.

7
src/docbkx/ops_mgt.xml
View File

@ -251,6 +251,13 @@ false
<para>TODO <para>TODO
</para> </para>
</section> </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"> <section xml:id="ops.backup">
<title >HBase Backup</title> <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. <para>There are two broad strategies for performing HBase backups: backing up with a full cluster shutdown, and backing up on a live cluster.