hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14232) Backwards compatiblity support for new MasterObserver APIs
Date Wed, 26 Aug 2015 00:39:45 GMT

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

Hadoop QA commented on HBASE-14232:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against master branch at commit 506726ed2832b069602c6b7e2ccd5ec9a81013a6.
  ATTACHMENT ID: 12752361

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15258//console

This message is automatically generated.

> 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
>            Assignee: Francis Liu
>              Labels: hbase-6721
>         Attachments: HBASE-14232_hbase-6721.patch
> 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

View raw message