hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Blaisdell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-725) Maximum ColumnKey Lookup
Date Mon, 07 Jul 2008 16:15:31 GMT

    [ https://issues.apache.org/jira/browse/HBASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611214#action_12611214

Daniel Blaisdell commented on HBASE-725:

Originally i was using timestamp as the one and only column key. This led to problems converting
from a data-based columnKey index to a 0-based for me as a developer. Not an impossible problem,
but nasty.

I switched approaches and created a columnFamily date: and now access all data via 0-based


instead of 

firstColumn:date, secondColumn:date

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

View raw message