You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "stack (JIRA)" <ji...@apache.org> on 2007/06/27 01:33:25 UTC

[jira] Created: (HADOOP-1534) [hbase] Memcache scanner fails if start key not present

[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


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.


[jira] Updated: (HADOOP-1534) [hbase] Memcache scanner fails if start key not present

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HADOOP-1534:
--------------------------

    Attachment: memcachescanner.patch

Patch memcache so rather than 'startsWith' looking for start key, we instead use compareTo exiting when current key is >= passed start key.

> [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.


[jira] Commented: (HADOOP-1534) [hbase] Memcache scanner fails if start key not present

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508370 ] 

Hadoop QA commented on HADOOP-1534:
-----------------------------------

+1

http://issues.apache.org/jira/secure/attachment/12360629/memcachescanner.patch applied and successfully tested against trunk revision r550952.

Test results:   http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/336/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/336/console

> [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.


[jira] Updated: (HADOOP-1534) [hbase] Memcache scanner fails if start key not present

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Commented: (HADOOP-1534) [hbase] Memcache scanner fails if start key not present

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508509 ] 

Hudson commented on HADOOP-1534:
--------------------------------

Integrated in Hadoop-Nightly #137 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/137/])

> [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.


[jira] Updated: (HADOOP-1534) [hbase] Memcache scanner fails if start key not present

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HADOOP-1534:
--------------------------

    Status: Patch Available  (was: Open)

> [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.