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

Hudson commented on YARN-7944:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13798 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13798/])
YARN-7944. [UI2] Remove master node link from headers of application (sunilg: 
rev 113f401f41ee575cb303ceb647bc243108d93a04)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/models/yarn-app.js
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/serializers/yarn-app-timeline.js
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/models/yarn-app-timeline.js
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/serializers/yarn-app.js
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/templates/yarn-app.hbs


> [UI2] Remove master node link from headers of application pages
> ---------------------------------------------------------------
>
>                 Key: YARN-7944
>                 URL: https://issues.apache.org/jira/browse/YARN-7944
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn-ui-v2
>    Affects Versions: 3.1.0
>            Reporter: Yesha Vora
>            Assignee: Yesha Vora
>            Priority: Major
>             Fix For: 3.1.0
>
>         Attachments: YARN-7944.001.patch, YARN-7944.002.patch, 
> YARN-7944.003.patch
>
>
> Rm UI2 has links for Master container log and master node. 
> This link published on application and service page. This links are not 
> required on all pages because AM container node link and container log link 
> are already present in Application view. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to