[
https://issues.apache.org/jira/browse/HBASE-14224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697183#comment-14697183
]
Lars George commented on HBASE-14224:
-------------------------------------
Easy to fix, in {{CoprocessorHost.loadSystemCoprocessors()}} changed this
{code}
if (findCoprocessor(className) != null) {
continue;
}
{code}
to something like this:
{code}
if (findCoprocessor(className) != null || configured.contains(className))
{
continue;
}
{code}
and in the shell's {{admin.rb}} change the code in {{alter}} to use
addCoprocessor - the whole "finding a new ID" is already taken care of in that
method anyways. So this also simplifies code.
Then check the other {{loadCoprocessors()}} classes to be safe too.
> Fix coprocessor handling of duplicate classes
> ---------------------------------------------
>
> Key: HBASE-14224
> URL: https://issues.apache.org/jira/browse/HBASE-14224
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
> Affects Versions: 2.0.0, 1.0.1, 1.2.0, 1.1.1
> Reporter: Lars George
> Attachments: problem.pdf
>
>
> While discussing with [~misty] over on HBASE-13907 we noticed some
> inconsistency when copros are loaded. Sometimes you can load them more than
> once, sometimes you can not. Need to consolidate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
