Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 17 Nov 2014 04:45:34 +0000 (UTC)
From: "James Taylor (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12753289.1415243270000.512709.1416199534764@Atlassian.JIRA>
In-Reply-To: <JIRA.12753289.1415243270000@Atlassian.JIRA>
References: <JIRA.12753289.1415243270000@Atlassian.JIRA>
 <JIRA.12753289.1415243270058@arcas>
Subject: [jira] [Commented] (HBASE-12433) Coprocessors not dynamically
 reordered when reset priority
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

James Taylor commented on HBASE-12433:
--------------------------------------

Here's the command we used to modify the priority of an existing coprocessor:
{code}
alter 'PHERF.PHERF_FIELD_HISTORY_ARCHIVE', METHOD => 'table_att', 'coprocessor$2' => '|org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver|1|'
{code}


> Coprocessors not dynamically reordered when reset priority
> ----------------------------------------------------------
>
>                 Key: HBASE-12433
>                 URL: https://issues.apache.org/jira/browse/HBASE-12433
>             Project: HBase
>          Issue Type: Bug
>          Components: Coprocessors
>    Affects Versions: 0.98.7
>            Reporter: James Taylor
>
> When modifying the coprocessor priority through the HBase shell, the order of the firing of the coprocessors wasn't changing. It probably would have with a cluster bounce, but if we can make it dynamic easily, that would be preferable.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)