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:39:56 GMT
Thanks Angus :).

But if it true, that i can get rid from version in qualifier (as
posted before) it
will be huge api simplification (my internal api), because my qualifier versions
duplicate hbase functionality.

2010/7/15 Angus He <angushe@gmail.com>:
> It is really a neat design.  :)
>
> On Thu, Jul 15, 2010 at 5:18 PM, Ryan Rawson <ryanobjc@gmail.com> wrote:
>> 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).
>>
>
>
>
> --
> Regards
> Angus
>

Mime
View raw message