You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "chunhui shen (JIRA)" <ji...@apache.org> on 2013/02/20 11:41:12 UTC
[jira] [Updated] (HBASE-7887) Support configuring KeyValue
Comparator as table level
[ https://issues.apache.org/jira/browse/HBASE-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chunhui shen updated HBASE-7887:
--------------------------------
Summary: Support configuring KeyValue Comparator as table level (was: Support configuring KeyValue Comparator as table)
> Support configuring KeyValue Comparator as table level
> ------------------------------------------------------
>
> Key: HBASE-7887
> URL: https://issues.apache.org/jira/browse/HBASE-7887
> Project: HBase
> Issue Type: New Feature
> Components: regionserver
> Affects Versions: 0.96.0
> Reporter: chunhui shen
> Assignee: chunhui shen
> Fix For: 0.96.0
>
>
> Now, KeyValue Comparator is static by code in HRegionInfo
> {code}
> public KVComparator getComparator() {
> return isRootRegion()? KeyValue.ROOT_COMPARATOR: isMetaRegion()?
> KeyValue.META_COMPARATOR: KeyValue.COMPARATOR;
> }
> {code}
> In some user cases, we need a personalized KeyValue Comparator.
> e.g. Current ByteArrayComparator couldn't be used to sort number if exists negative number.(Because the bytes of -1 is bigger than the bytes of any other number)
> I think supporting per-table configuration of KeyValue Comparator would be useful.
> Welcome comments,
> I will make the patch tomorrow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira