You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2015/10/06 09:22:26 UTC

[jira] [Updated] (AMBARI-13316) Stack Advisor for hive.security.authorization.manager with Ranger enabled is not specific enough

     [ https://issues.apache.org/jira/browse/AMBARI-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gautam Borad updated AMBARI-13316:
----------------------------------
    Affects Version/s:     (was: 2.1.3)
                       2.1.1

> 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
>
>
> 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)