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

HBASE-10441 [docs] nit default max versions is now 1 instead of 3 afte rHBASe-8450 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1562663 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jonathan Hsieh 2014-01-30 01:11:54 +00:00
parent 475420205c
commit ca175589f5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/docbkx/schema_design.xml
View File

@ -753,7 +753,7 @@ reasonable spread in the keyspace, similar options appear:
</para>
<section xml:id="schema.smackdown.rowsversions"><title>Rows vs. Versions</title>
<para>A common question is whether one should prefer rows or HBase's built-in-versioning. The context is typically where there are
"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 1 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>Preference: Rows (generally speaking).