[
https://issues.apache.org/jira/browse/TEZ-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306334#comment-14306334
]
Prakash Ramachandran commented on TEZ-2018:
-------------------------------------------
bq. why cannot tracking url ( while the app is still running ) be set to the
final history url if webservices are disabled? Does the proxy end up creating
problems?
couple of issues. 1) the webappproxy servlet will proxy the contents (as far as
the browser is concerned it would be comming from http://rmproxy:8088), this
will have issues with js/css etc 2) it would assume that resource manager can
reach the uihost.
bq. Does TEZ_VERSION need to be supported as a replacement var in the url if
the UI becomes version dependent?
will look at it and add, more importantly will need to add it to response.
bq. MAX_VERTICES_QUERIED handling - silently ignores a list larger than 100?
wanted to put an upper limit. currently ui will not query for a vertex size of
more than 50 (batched). so this should be fine. will fix it in a followup.
> Job Tracking and History URL should point to the Tez UI
> -------------------------------------------------------
>
> Key: TEZ-2018
> URL: https://issues.apache.org/jira/browse/TEZ-2018
> Project: Apache Tez
> Issue Type: New Feature
> Components: UI
> Reporter: Rohini Palaniswamy
> Assignee: Prakash Ramachandran
> Priority: Critical
> Attachments: TEZ-2018.1.patch, TEZ-2018.2.patch, TEZ-2018.3.patch,
> TEZ-2018.4.patch, TEZ-2018.wip.1.patch
>
>
> We need to have the Job Tracking URL take users to the Tez UI if
> yarn.timeline-service.enabled=true
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
