[
https://issues.apache.org/jira/browse/HBASE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629844#action_12629844
]
Jim Kellerman commented on HBASE-859:
-------------------------------------
+1
Yes, with separate fields, we wouldn't have to parse the keys, which worked for
Text, but not for binary row keys.
For METAHSK I would have table, startkey, endkey. With the right compareTo
method we would know how to sort the keys so that the children of a split would
come after the parent.
I'd also like to get rid of the region id, since it was only used for sorting
purposes.
> HStoreKey needs a reworking
> ---------------------------
>
> Key: HBASE-859
> URL: https://issues.apache.org/jira/browse/HBASE-859
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Critical
>
> HBASE-832 had to make an ugly hack to address fact that rows that included
> the delimiter -- or a byte < delimiter -- messed up sorting in .META. Fix
> the ugly hack, and while we're at it, add a byte for flags to the HSK so can
> mark if key is a meta key, a delete key (cell/family/row), etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
