Hi, I just saw your recent update of the hbase book on the version number
question, and I'm also confused about it.
As said on the book (HBASE-4251), it is not recommended setting the number
of versions to an exceedingly high level (e.g., hundreds or more) unless
those old values are very dear to
-Mike
Date: Fri, 26 Aug 2011 16:37:46 +0800
Subject: Re: Versioning
From: chensheng2...@gmail.com
To: user@hbase.apache.org
Hi, I just saw your recent update of the hbase book on the version number
question, and I'm also confused about it.
As said on the book (HBASE-4251
in separate rows.
Dave
-Original Message-
From: Sheng Chen [mailto:chensheng2...@gmail.com]
Sent: Friday, August 26, 2011 1:38 AM
To: user@hbase.apache.org
Subject: Re: Versioning
Hi, I just saw your recent update of the hbase book on the version number
question, and I'm also confused about
AM
To: user@hbase.apache.org
Subject: Re: Versioning
Hi, I just saw your recent update of the hbase book on the version number
question, and I'm also confused about it.
As said on the book (HBASE-4251), it is not recommended setting the number
of versions to an exceedingly high level (e.g
-Original Message-
From: Sheng Chen [mailto:chensheng2...@gmail.com]
Sent: Friday, August 26, 2011 1:38 AM
To: user@hbase.apache.org
Subject: Re: Versioning
Hi, I just saw your recent update of the hbase book on the version
number
question, and I'm also confused about it.
As said on the book
Versioning can be used to see the previous state of a record. Some people
need this feature, others don't.
One thing that may be worth a review is this...
http://hbase.apache.org/book.html#keysize
... and specifically the fact about all the values being freighted with
timestamp (aka version)
