You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Daniel Blaisdell (JIRA)" <ji...@apache.org> on 2008/07/07 16:43:31 UTC
[jira] Created: (HBASE-725) Maximum ColumnKey Lookup
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.2.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.
[jira] Updated: (HBASE-725) Maximum ColumnKey Lookup
Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HBASE-725) Maximum ColumnKey Lookup
Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611209#action_12611209 ]
Bryan Duxbury commented on HBASE-725:
-------------------------------------
It doesn't matter if the timestamp part of the qualifier can be anything. Getting the last by lexical sort should be easy.
> 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.2.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.
[jira] Commented: (HBASE-725) Maximum ColumnKey Lookup
Posted by "Daniel Blaisdell (JIRA)" <ji...@apache.org>.
[ 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 columnKeys.
firstColumn:0,secondColumn:0,date:0
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.
[jira] Commented: (HBASE-725) Maximum ColumnKey Lookup
Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611205#action_12611205 ]
Jim Kellerman commented on HBASE-725:
-------------------------------------
By time series relative column keys, are you talking about the row timestamp, or are you storing the data as family:nnnnnnnnn where nnnnnnnnn is the timestamp?
If the latter, there is no good way to search for the "last" one, because the part of the column key after the ':' can be anything. If you are storing time series data I would recommend using the row timestamp because each cell is addressed by row/family:member/timestamp
> 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.2.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.
[jira] Updated: (HBASE-725) Maximum ColumnKey Lookup
Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
[ 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.18.0)
0.19.0
> 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.19.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.
[jira] Updated: (HBASE-725) Maximum ColumnKey Lookup
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-725:
------------------------
Fix Version/s: (was: 0.20.0)
Moving out of 0.20.0. Its minor and the reporter found a workaround.
> 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
>
> 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.
[jira] Updated: (HBASE-725) Maximum ColumnKey Lookup
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-725:
------------------------
Fix Version/s: (was: 0.19.0)
0.20.0
Moving out of 0.19.0.
> 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.20.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.