[
https://issues.apache.org/jira/browse/AMBARI-9602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318819#comment-14318819
]
Hadoop QA commented on AMBARI-9602:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12698464/0001-AMBARI-9602-Stack-advisor-validation-for-Ranger-HBas.patch
against trunk revision .
{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 tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1662//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1662//console
This message is automatically generated.
> Stack advisor validation for Ranger HBase plugin is incorrect
> -------------------------------------------------------------
>
> Key: AMBARI-9602
> URL: https://issues.apache.org/jira/browse/AMBARI-9602
> Project: Ambari
> Issue Type: Bug
> Reporter: Velmurugan Periasamy
> Assignee: Velmurugan Periasamy
> Attachments:
> 0001-AMBARI-9602-Stack-advisor-validation-for-Ranger-HBas.patch
>
>
> The stack advisor validation when Ranger HBase plugin enabled are incorrect.
> The problem with the current approach is that it checks for an exact match
> against com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor for
> hbase.coprocessor.master.classes and hbase.coprocessor.region.classes;
> however, these are comma-delimited lists, so there could be other classes
> defined that the user needs.
> The stack advisor should be checking to see the following when the Ranger
> plugin is enabled for HBase:
> * hbase.coprocessor.master.classes contains
> com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor and does
> not contain org.apache.hadoop.hbase.security.access.AccessController
> * hbase.coprocessor.region.classes contains
> com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor and does
> not contain org.apache.hadoop.hbase.security.access.AccessController
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
