You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2011/04/08 03:59:06 UTC

[jira] [Updated] (HBASE-3624) Only one coprocessor of each priority type can be loaded for a table

     [ https://issues.apache.org/jira/browse/HBASE-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-3624:
----------------------------------

    Attachment: HBASE-3624.patch

> Only one coprocessor of each priority type can be loaded for a table
> --------------------------------------------------------------------
>
>                 Key: HBASE-3624
>                 URL: https://issues.apache.org/jira/browse/HBASE-3624
>             Project: HBase
>          Issue Type: Bug
>          Components: coprocessors
>    Affects Versions: 0.92.0
>         Environment: Standalone HBase, linux
>            Reporter: Jesse Daniels
>            Assignee: Andrew Purtell
>         Attachments: HBASE-3624.patch
>
>
> Coprocessors are added to HBase using a TreeSet that is initialized with an EnvironmentPriorityComparator. The net effect is that only one coprocessor of a given priority can be loaded at a time for a given table. This appears to be due to how the TreeSet uses the EnvironmentPriorityComparator to determine whether there are duplicate entries - if the coprocessors have the same priority (e.g., User), they are considered the same and won't be added to the Set.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira