[
https://issues.apache.org/jira/browse/AMBARI-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948269#comment-14948269
]
Hudson commented on AMBARI-13316:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3612 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3612/])
AMBARI-13316. Stack Advisor for hive.security.authorization.manager with
(gborad:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e9389246dc3dbe98eccf32e8ad89eca808e6438f])
* ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
*
ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-ugsync-site.xml
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
> Stack Advisor for hive.security.authorization.manager with Ranger enabled is
> not specific enough
> ------------------------------------------------------------------------------------------------
>
> Key: AMBARI-13316
> URL: https://issues.apache.org/jira/browse/AMBARI-13316
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.1
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 2.1.3
>
> Attachments: AMBARI-13316.patch
>
>
> Making changes to Hive with Ranger enabled and the incorrect value for
> hive.security.authorization.manager raises a warning that this value is not
> set correctly. This is good and expected. The issue is that the warning is
> not specific enough, and does not call out that this settings needs to be
> made under hiveserver2-site. This might lead the customer to change the
> general hive.security.authorization.manager setting, breaking Hive CLI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
