[ 
https://issues.apache.org/jira/browse/AMBARI-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946931#comment-14946931
 ] 

Hadoop QA commented on AMBARI-13316:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12765325/AMBARI-13316.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {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/3916//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3916//console

This message is automatically generated.

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

Reply via email to