[
https://issues.apache.org/jira/browse/HBASE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629645#action_12629645
]
Jonathan Gray commented on HBASE-661:
-------------------------------------
Clint,
Check out HBASE-832, HBASE-868, and HBASE-877. These all deal directly with
comparators and rows in the meta table.
There's a consensus after dealing with these issues that we'll be doing an
overhaul of some kind of the comparators associated with each region.
I imagine this issue would be solved along with that change.
> Allow to specify a user supplied row key comparator for a table
> ----------------------------------------------------------------
>
> Key: HBASE-661
> URL: https://issues.apache.org/jira/browse/HBASE-661
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: client, master, regionserver
> Affects Versions: 0.2.0
> Reporter: Clint Morgan
> Assignee: Clint Morgan
>
> Now that row keys are byte arrays, users should be able to specify a
> comparator at table creation time.
> My use case for this is to implement secondary indexes. In this case, row
> keys for the index tables will be constructed from an optional prefix of the
> original row key as well as the content of column that is being indexed. Then
> the comparator will first compare based on the key prefix, and break ties by
> deserializing the column values and using the deserialized type's compareTo
> method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
