[
https://issues.apache.org/jira/browse/YARN-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771561#comment-13771561
]
Raghavendra Nandagopal commented on YARN-1216:
----------------------------------------------
Hi Joshi
I am new to YARN community and would like start contributing.
Looking at the above change, here are the findings.
1) We should move the methods to a new class under the below util package.
package org.apache.hadoop.yarn.util;
2) Create a new class, what would be the new name (say YarnManagerURLs or
YarnURLs)
3) Also it is mentioned to mark it has private, should we use singleton
instance and then call the methods that are private for the class.
3) Will this class be wrapper and the calls will still continue to go through
the existing methods that are declared in the YarnConfiguration or do we need
to change wherever the methods are called.
4) Should we write any additional test methods after the change based on the
outcome of 3rd point above.
> Deprecate/ mark private few methods from YarnConfiguration
> ----------------------------------------------------------
>
> Key: YARN-1216
> URL: https://issues.apache.org/jira/browse/YARN-1216
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Omkar Vinit Joshi
> Priority: Minor
> Labels: newbie
>
> Today we have few methods in YarnConfiguration which should ideally be moved
> to some utility class.
> [related comment |
> https://issues.apache.org/jira/browse/YARN-1203?focusedCommentId=13771281&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13771281
> ]
> * getRMWebAppURL
> * getRMWebAppHostAndPort
> * getProxyHostAndPort
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
