hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Segel <michael_se...@hotmail.com>
Subject Re: Key Value collision
Date Thu, 16 May 2013 20:50:21 GMT
Yes, but that wasn't what he asked. ;-)


On May 16, 2013, at 3:05 PM, Jeff Kolesky <jeff@opower.com> wrote:

> Except in the case of bulk loads; if you import cells with the same
> timestamp through a bulk load, the "last row" is non-deterministic.
> Facebook fixed the issue, and the patch has been backported to 0.95.  The
> friendly folks at Cloudera are working on backporting the fix to 0.94 as
> well.
> 
> Follow https://issues.apache.org/jira/browse/HBASE-8521 for the 0.94
> backport progress if it is of interest to you.
> 
> Jeff
> 
> 
> On Thu, May 16, 2013 at 12:00 PM, Michael Segel
> <michael_segel@hotmail.com>wrote:
> 
>> Last row inserted wins.
>> 
>> On May 16, 2013, at 1:49 PM, Varun Sharma <varun@pinterest.com> wrote:
>> 
>>> Hi,
>>> 
>>> I am wondering what happens when we add the following:
>>> 
>>> row, col, timestamp --> v1
>>> 
>>> A flush happens. Now, we add
>>> 
>>> row, col, timestamp --> v2
>>> 
>>> A flush happens again. In this case if MAX_VERSIONS == 1, how is the tie
>>> broken during reads and during minor compactions, is it arbitrary ?
>>> 
>>> Thanks
>>> Varun
>> 
>> 
> 
> 
> -- 
> *Jeff Kolesky*
> Chief Software Architect
> *Opower*


Mime
View raw message