hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prakash Khemani (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-3396) getLastIncrement() can miss some key-values
Date Thu, 30 Dec 2010 02:25:45 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Prakash Khemani resolved HBASE-3396.

      Resolution: Not A Problem
    Release Note: maxVersion in the scan is set to 1

> getLastIncrement() can miss some key-values
> -------------------------------------------
>                 Key: HBASE-3396
>                 URL: https://issues.apache.org/jira/browse/HBASE-3396
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.0
>            Reporter: Prakash Khemani
>            Assignee: Jonathan Gray
> In getLastIncrement() there is an assumption that memstore only scan will never return
multiple versions of a kv
>     // found everything we were looking for, done
>     if (results.size() == expected) {
>       return results;
>     }
> Based on this assumption the code does an early out after it finds the expected number
of key-value pairs in the memstore. But what if there were multiple versions of the same kv
returned by the memstore scan? I think it is possible when the memstore has a snapshot pending
to be written out. A version of the key can be returned each from the online and from the
snapshot memory.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message