[
https://issues.apache.org/jira/browse/HBASE-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017243#comment-13017243
]
Gary Helmling commented on HBASE-3624:
--------------------------------------
+1
In CoprocessorHost, though, I don't think we need this change:
{noformat}
- public E load(Path path, String className, Coprocessor.Priority priority)
+ public E load(Path path, String className, Coprocessor.Priority priority,
int seq)
{noformat}
since the counter will still be incremented down in loadInstance()? You want
to remove it (and usage in RegionCoprocessorHost.loadTableCoprocessors()) on
commit?
> 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
