[
https://issues.apache.org/jira/browse/AMBARI-9602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318797#comment-14318797
]
Hudson commented on AMBARI-9602:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1753 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1753/])
AMBARI-9602. Fix Stack advisor validation for Ranger HBase plugin. (Velmurugan
Periasamy via yusaku) (yusaku:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5f351bace30506539e3c443f32f9226cd8e33e14)
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
> 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)
