You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2008/08/22 01:20:44 UTC

[jira] Updated: (HBASE-605) allow scanners which return results ordred by a column value

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

Jim Kellerman updated HBASE-605:
--------------------------------

    Fix Version/s:     (was: 0.18.0)
                   0.19.0

> allow scanners which return results ordred by a column value
> ------------------------------------------------------------
>
>                 Key: HBASE-605
>                 URL: https://issues.apache.org/jira/browse/HBASE-605
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: client, regionserver
>    Affects Versions: 0.2.0
>            Reporter: Clint Morgan
>            Priority: Minor
>             Fix For: 0.19.0
>
>         Attachments: hbase-605-v2.patch, hbase-605-v3.patch, hbase-605.patch
>
>
> We would like to be able to scan though tables with results ordered by (deserialized) column values. This approach maintains an in-memory sorted set for each ordered-by column in each HStore. This allows us to iterate through the keys in column order, and to random reads on the key to get the full row.
> Without the index, then we have to scan through all the rows to get the first result ordered by a column. Thus, when R is the number of rows in a table,  N is the number of ordered-by rows we want, and R >> N we can save a lot of work by not doing the full table scan.

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