[
https://issues.apache.org/jira/browse/TEZ-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305843#comment-14305843
]
Hitesh Shah commented on TEZ-2018:
----------------------------------
Mostly looks good. [~jeagles] any comments on the patch?
Some comments which I think can be followed up in a separate jira:
- 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?
- still have concerns on the need of the flag - should rethink this before
the 0.6.1 release
- Does TEZ_VERSION need to be supported as a replacement var in the url if
the UI becomes version dependent?
- MAX_VERTICES_QUERIED handling - silently ignores a list larger than 100?
> 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)
