Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> Key Value collision


Copy link to this message
-
Re: Key Value collision
Yes, but that wasn't what he asked. ;-)
On May 16, 2013, at 3:05 PM, Jeff Kolesky <[EMAIL PROTECTED]> 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
> <[EMAIL PROTECTED]>wrote:
>
>> Last row inserted wins.
>>
>> On May 16, 2013, at 1:49 PM, Varun Sharma <[EMAIL PROTECTED]> 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*