[
https://issues.apache.org/jira/browse/AMBARI-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028435#comment-15028435
]
Hadoop QA commented on AMBARI-14058:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12774484/AMBARI-14058_branch-2.1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4402//console
This message is automatically generated.
> Tez Ambari View: The "Application Tracking URL" in Tez Application
> Description Table should point to RM
> -------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-14058
> URL: https://issues.apache.org/jira/browse/AMBARI-14058
> Project: Ambari
> Issue Type: Bug
> Reporter: Sreenath Somarajapuram
> Assignee: DIPAYAN BHOWMICK
> Priority: Critical
> Attachments: 1.jpg, 2.jpg, AMBARI-14058_branch-2.1.patch
>
>
> In Tez ATS 1.5, we see in the Application Tracking URL points to Ambari UI.
> Attached are the screenshots.
> rmproxy is designed to handle only JSON data.
> Guess the best available option would be to send back a 301 redirect if the
> content cannot be parsed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
