Re: Key Value collision

2013-05-17 Thread Stack
On Thu, May 16, 2013 at 11:49 AM, Varun Sharma va...@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

Key Value collision

2013-05-16 Thread Varun Sharma
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

Re: Key Value collision

2013-05-16 Thread Michael Segel
Last row inserted wins. On May 16, 2013, at 1:49 PM, Varun Sharma va...@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

Re: Key Value collision

2013-05-16 Thread Jeff Kolesky
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