You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sreenath Somarajapuram (JIRA)" <ji...@apache.org> on 2015/11/25 09:35:11 UTC

[jira] [Commented] (AMBARI-14058) Tez Ambari View: The "Application Tracking URL" in Tez Application Description Table should point to RM

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

Sreenath Somarajapuram commented on AMBARI-14058:
-------------------------------------------------

[~dbhowmick]
Please add the following to init-ambari-view.js (line 167), at the same level of restNamespace.
{code}
  otherNamespace: {
      cluster: '%@rmproxy/cluster'.fmt(resourcesPrefix)
  },
{code} 

> 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
>
>
> 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)