You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/07/30 06:39:31 UTC

[jira] Resolved: (HBASE-783) For single row, single family retrieval, getRow() works half as fast as getScanner().next()

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

stack resolved HBASE-783.
-------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.2.1)
                       (was: 0.3.0)
                   0.2.0

Committed.  Thanks for the patch J-D.

> For single row, single family retrieval, getRow() works half as fast as getScanner().next()
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-783
>                 URL: https://issues.apache.org/jira/browse/HBASE-783
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.2.0
>            Reporter: Jonathan Gray
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.2.0
>
>         Attachments: hbase-783-v1.patch
>
>
> We have a very typical use-case of wanting to retrieve all columns under a single row, single family.
> Benchmarking regularly reproduces the same result.  Using HTable.getScanner().next() to get the RowResult works twice as fast as HTable.getRow().
> This is related to HBASE-631 by jdcryans which added this functionality to getRow().

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