[
https://issues.apache.org/jira/browse/HBASE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648828#action_12648828
]
apurtell edited comment on HBASE-883 at 11/18/08 4:16 PM:
----------------------------------------------------------------
Third time will be the charm. We took out the custom comparators because we can
see them acting as a tax on the rest of HRS: 5-10% CPU, 20% of all object
allocation (on a jgray server). But the custom comparators are used to reverse
a test to provide descending sort orders. For now we'll degrade the secondary
index capability somewhat by fixing it up to work without the custom
comparators, hence no descending sort ordering.
was (Author: apurtell):
Third time will be the charm. We took out the custom comparators because we
can see them acting as a tax on the rest of HRS: 5-10% CPU, 20% of all object
allocation (on a jgray server). But the custom comparators are used to reverse
a test to provide descending sort orders. For now we'll degrade the secondary
index capability somewhat by fixing it up to work with the custom comparators
hence no descending sort ordering.
> Secondary Indexes
> -----------------
>
> Key: HBASE-883
> URL: https://issues.apache.org/jira/browse/HBASE-883
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: client, regionserver
> Reporter: Clint Morgan
> Assignee: Andrew Purtell
> Fix For: 0.19.0
>
> Attachments: hbase-883.patch, hbase-883.patch, hbase-883.patch,
> hbase-883.patch, hbase-883.patch, hbase-883.patch, hbase-883.patch,
> secondary.patch
>
>
> I'm working on a secondary index impl. The basic idea is to maintain a
> separate table per index.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
