No, you're right.
But if you just want to keep "500" as the value, you just have to set
the number of version to 1 for your table...
If you just want to keep 100, then you can insert with a revert
timestamp, so the last cell inserted will be hidden by the previous
one.
JM
2012/10/11, Narayanan
Hi,
I have 2 column families A and B in table T1.
put 'T1', 'R1', 'A:qualf1',100
put 'T1', R1', 'B:qualf2', 200
As per my understanding the above is one row and one single version each
for the 2 column families.
If I do a put 'T1', 'R1', 'A:qualf1', 500, then there is another version
for the ro
Correct.
If you do 2 Puts for row key A-B-C-D on different days, the second Put
logically replaces the first and the earlier Put becomes a previous
version. Unless you specifically want older versions, you won't get them
in either Gets or Scans.
Definitely want to read thisŠ
http://hbase.apach
correct me if I'm wrong. The version applies to the individual cell (ie.
row key, column family and column qualifier) not (row key, column family).
On Wed, Oct 10, 2012 at 3:13 PM, Narayanan K wrote:
> Hi all,
>
> I have a usecase wherein I need to find the unique of some things in HBase
> acro
Hi all,
I have a usecase wherein I need to find the unique of some things in HBase
across dates.
Say, on 1st Oct, A-B-C-D appeared, hence I insert a row with rowkey :
A-B-C-D.
On 2nd Oct, I get the same value A-B-C-D and I don't want to redundantly
store the row again with a new rowkey - A-B-C-D
