Wangda Tan commented on YARN-3368:

My thought for this: we should include this in branch-2 to avoid divergence 
between trunk and branch-2, UI code should be relatively independent. New 
UI/old UI should be able to run together without affecting each other, and the 
new UI will be disabled by default.

I'm not quite sure what did you mean by "it would break folks who scrape the 
site today."


> Improve YARN web UI
> -------------------
>                 Key: YARN-3368
>                 URL: https://issues.apache.org/jira/browse/YARN-3368
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Jian He
>         Attachments: Applications-table-Screenshot.png, 
> Queue-Hierarchy-Screenshot.png, YARN-3368.poc.1.patch
> The goal is to improve YARN UI for better usability.
> We may take advantage of some existing front-end frameworks to build a 
> fancier, easier-to-use UI. 
> The old UI continue to exist until  we feel it's ready to flip to the new UI.
> This serves as an umbrella jira to track the tasks. we can do this in a 
> branch.

This message was sent by Atlassian JIRA

Reply via email to