ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14058) Tez Ambari View: The "Application Tracking URL" in Tez Application Description Table should point to RM
Date Tue, 01 Dec 2015 19:49:11 GMT

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

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/12775043/AMBARI-14058.2_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/4436//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
>          Components: ambari-views
>            Reporter: Sreenath Somarajapuram
>            Assignee: DIPAYAN BHOWMICK
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: 1.jpg, 2.jpg, AMBARI-14058.2_branch-2.1.patch, 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)

Mime
View raw message