Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 18 Aug 2015 16:28:45 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12856701.1439838055000.96458.1439915325830@Atlassian.JIRA>
In-Reply-To: <JIRA.12856701.1439838055000@Atlassian.JIRA>
References: <JIRA.12856701.1439838055000@Atlassian.JIRA>
 <JIRA.12856701.1439838055841@arcas>
Subject: [jira] [Commented] (HBASE-14232) Backwards compatiblity support for
 new MasterObserver APIs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-14232:
----------------------------------------

bq. We can generically do this for all types of CPs? So later on we can add hooks to CPs with out worry for BC.
We already have some reusable support for this from when Sean updated the WALObserver. It's reasonable to aim for as much reuse as we can get when doing the work here.

> Backwards compatiblity support for new MasterObserver APIs
> ----------------------------------------------------------
>
>                 Key: HBASE-14232
>                 URL: https://issues.apache.org/jira/browse/HBASE-14232
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>              Labels: hbase-6721
>
> The group assignment changes introduce new methods to the MasterObserver interface. This is a concern for things like Apache Phoenix. (See their IndexMasterObserver, etc.) We can handle this by using compatibility helpers that won't attempt to invoke the new APIs on MasterObservers that do not implement them. 


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