[
https://issues.apache.org/jira/browse/AMBARI-14058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035445#comment-15035445
]
Hudson commented on AMBARI-14058:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #3950 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3950/])
AMBARI-14058. "Application Tracking URL" in Tez View broken due to RM HA
(yusaku:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=29264fabf08ca8fea7be48d17a3670581125ad1a])
* contrib/views/tez/src/main/resources/ui/scripts/init-ambari-view.js
*
contrib/views/tez/src/main/java/org/apache/ambari/view/tez/rest/BaseRedirectionResource.java
*
contrib/views/tez/src/main/java/org/apache/ambari/view/tez/rest/BaseProxyResource.java
*
contrib/views/tez/src/main/java/org/apache/ambari/view/tez/rest/RMRedirectResource.java
* contrib/views/tez/src/main/resources/view.xml
> 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)
