ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sreenath Somarajapuram (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-14058) Tez Ambari View: The "Application Tracking URL" in Tez Application Description Table should point to RM
Date Wed, 25 Nov 2015 08:29:11 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sreenath Somarajapuram updated AMBARI-14058:
--------------------------------------------
    Description: 
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.

  was:
In Tez ATS 1.5, we see in the Application Tracking URL points to Ambari UI.
Attached are the screenshots.


> 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
>            Priority: Critical
>         Attachments: 1.jpg, 2.jpg
>
>
> 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