hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Stepachev <oct...@gmail.com>
Subject Re: Is it safe to use timestamps (or versions) to load old values.
Date Thu, 15 Jul 2010 09:34:06 GMT
Do i understand correct, that if i do:

put('table', 'family', 'qual', 'value1', asTimestamp('2009-01-01'))
put('table', 'family', 'qual', 'value2', now())
put('table', 'family', 'qual', 'value1', asTimestamp('2009-01-01'))

i get value2 in any scan after second put?

2010/7/15 Ryan Rawson <ryanobjc@gmail.com>:
> As of hbase 0.20.5 gets no longer return the wrong value... They are now
> always correct like scans - because they internally are 1 row scans.
>
> On Jul 15, 2010 1:44 AM, "Andrey Stepachev" <octo47@gmail.com> wrote:
>> By mistake email was sent ;).
>>
>> To be more specific, here is example of my schema
>>
>> table bsn.main:
>> key: long
>> family: names
>> type:date:version => json object
>> family: addresses
>> type:date:version => json object
>> etc.
>>
>> so, loader can put old name into names with old data (even if some
>> name json object was updated).
>> in such case i increment version and later remove multiple version (to
>> save space and time).
>

Mime
View raw message