[
https://issues.apache.org/jira/browse/AMBARI-14785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115153#comment-15115153
]
Hadoop QA commented on AMBARI-14785:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12784128/AMBARI-14785_branch-2.2.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:red}-1 core tests{color}. The test build failed in
contrib/views/hive
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5039//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5039//console
This message is automatically generated.
> Hive View: "NO DAG Available" on TEZ tab when ambari is running behind proxy
> ----------------------------------------------------------------------------
>
> Key: AMBARI-14785
> URL: https://issues.apache.org/jira/browse/AMBARI-14785
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.2.0
> Reporter: Gaurav Nagar
> Assignee: Gaurav Nagar
> Attachments: AMBARI-14785.2_branch-2.2.patch,
> AMBARI-14785_branch-2.2.patch
>
>
> Tez dag is not available when ambari is running behind proxy.
> We are getting tez url from ambari api.
> Response of http://proxyhost:port/api/v1/views/TEZ
> {
> "href": "http://ambarihost:port/api/v1/views/TEZ";,
> "ViewInfo": {
> "view_name": "TEZ"
> },
> "versions": [{
> "href":
> "http://ambarihost:port/api/v1/views/TEZ/versions/0.7.0.2.3.2.0-430";,
> "ViewVersionInfo": {
> "version": "0.7.0.2.3.2.0-430",
> "view_name": "TEZ"
> }
> }]
> }
> The href field is used to get tez url which is not accessible from outside.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
