hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1534) [hbase] Memcache scanner fails if start key not present
Date Wed, 27 Jun 2007 04:52:26 GMT

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

stack updated HADOOP-1534:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed with below message.

HADOOP-1534. [hbase] Memcache scanner fails if start key not present
* src/contrib/hbase/src/java/org/apache/hadoop/hbase/HMemcache.java
    (findFirstRow): Change compare from startsWith -- looking for
    an 'exact' match -- to instead use compareTo and if >= 0, then
    we are at first key.
* src/contrib/hbase/src/java/org/apache/hadoop/hbase/HRegionServer.java
    Add logging of problematic directory if server won't start because
    log file exists.

> [hbase] Memcache scanner fails if start key not present
> -------------------------------------------------------
>                 Key: HADOOP-1534
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1534
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: stack
>            Assignee: stack
>         Attachments: memcachescanner.patch
> If you specify a start key for a scanner that does not exist in the store, scanner returns
zero records even though there may be plenty keys > than supplied first key.

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

View raw message