Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 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
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
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB