[
https://issues.apache.org/jira/browse/AMBARI-16084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256857#comment-15256857
]
Hudson commented on AMBARI-16084:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #4732 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4732/])
AMBARI-16084. [RU] Hbase is losing table access permissions during
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=51cd067b056adb1013a168b59b8d65d1e2946a0c])
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
> [RU] Hbase is losing table access permissions during upgrade.
> -------------------------------------------------------------
>
> Key: AMBARI-16084
> URL: https://issues.apache.org/jira/browse/AMBARI-16084
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.2
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.2.2
>
> Attachments: AMBARI-16084.patch
>
>
> So here's where we are:
> - https://reviews.apache.org/r/45890/diff/2#index_header removed hard-coded
> python code which was trying to figure out which coprocessor to use. With
> these values gone, it's now up to Ambari to set the _right_ value in the
> configurations.
> - However, after removing the above code, we never change the ranger
> configurations to reflect the proper value
> - To fix this, we need to fix the values on Ambari upgrade. When upgrading
> Ambari from 2.0, we'll need to do the following:
> -- If Ranger is disabled; do nothing
> -- If Ranger is enabled and the cluster's current stack is HDP 2.2, then set
> the master/region coprocessors to
> {code}
> hbase_coprocessor_master_classes =
> "com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor"
> hbase_coprocessor_regionserver_classes =
> "com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor"
> hbase_coprocessor_region_classes =
> "org.apache.hadoop.hbase.security.token.TokenProvider,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor"
> {code}
> -- If Ranger is enabled and the cluster's current stack is HDP 2.3, then set
> the master/region coprocessors to
> {code}
> hbase_coprocessor_master_classes =
> "org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor "
> hbase_coprocessor_regionserver_classes =
> "org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor"
> hbase_coprocessor_region_classes =
> "org.apache.hadoop.hbase.security.token.TokenProvider,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor"
> {code}
> Now HDP stack upgrades will work since we look for
> {{XaSecureAuthorizationCoprocessor}} and change it to
> {{RangerAuthorizationCoprocessor}} as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
