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/07/07 18:13:31 UTC

[jira] Updated: (HBASE-725) Maximum ColumnKey Lookup

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

Jim Kellerman updated HBASE-725:
--------------------------------

    Fix Version/s:     (was: 0.2.0)
                   0.3.0

Marking for 0.3.0 since we would like to post a release candidate for 0.2.0 sooner rather than later.

> Maximum ColumnKey Lookup
> ------------------------
>
>                 Key: HBASE-725
>                 URL: https://issues.apache.org/jira/browse/HBASE-725
>             Project: Hadoop HBase
>          Issue Type: New Feature
>            Reporter: Daniel Blaisdell
>            Priority: Minor
>             Fix For: 0.3.0
>
>
> When working with time series data, relative columnKeys 'indexes' are routinely shared between the columnFamilies of a given row. To acquire the maximum key and increment it for the next columnKey, you must first get all the keys. A quick lookup of the last columnKey would benefit as the column size grows over time. 

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