hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3624) Only one coprocessor of each priority type can be loaded for a table
Date Tue, 12 Apr 2011 09:30:06 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018777#comment-13018777
] 

Hudson commented on HBASE-3624:
-------------------------------

Integrated in HBase-TRUNK #1846 (See [https://hudson.apache.org/hudson/job/HBase-TRUNK/1846/])
    

> 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
>             Fix For: 0.92.0
>
>         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

Mime
View raw message