[
https://issues.apache.org/jira/browse/AMBARI-12189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604554#comment-14604554
]
Hadoop QA commented on AMBARI-12189:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12742373/AMBARI-12189.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/3299//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3299//console
This message is automatically generated.
> hive.security.authorization.enabled is not being handled properly during
> Ambari upgrade
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-12189
> URL: https://issues.apache.org/jira/browse/AMBARI-12189
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
> Affects Versions: 2.1.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12189.patch
>
>
> After upgrade, ranger authorization and auditing are broken because Hive
> Authorization parameters are not migrated properly. Especially
> hive.security.authorization.enabled (in hiveserver2-site.xml) is set to False.
> if {{hive-env/hive_security_authorization}} is "Ranger" then
> {{hive.security.authorization.enabled}} should be true.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
