[
https://issues.apache.org/jira/browse/AMBARI-17271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334185#comment-15334185
]
Hadoop QA commented on AMBARI-17271:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12811064/AMBARI-17271.branch-2.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 core tests{color}. The test build failed in
contrib/views/hive-next
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7378//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7378//console
This message is automatically generated.
> Hive Jdbc View: Add code to include 'hive.server2.proxy.user' to connection
> param by default
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-17271
> URL: https://issues.apache.org/jira/browse/AMBARI-17271
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.4.0
> Reporter: DIPAYAN BHOWMICK
> Assignee: DIPAYAN BHOWMICK
> Fix For: 2.4.0
>
> Attachments: AMBARI-17271.branch-2.4.patch
>
>
> To make the instances work in kerberized environment, we need to add the
> proxy user in the session params which will go with the connection url.
> To make this seemless we need to add the 'hive.server2.proxy.user" parameter
> to the jdbc url in the kerberized cluster if user has not provided it in
> session parameter configuration while creating the instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
