[
https://issues.apache.org/jira/browse/YARN-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700519#comment-13700519
]
Abhishek Kapoor commented on YARN-855:
--------------------------------------
Agree with you Siddharth.
Just a thought, wouldn't it be more logical to enforce YarnClient to accept
YarnConfiguration as a parameter, rather then checking existence of all the
parameters in YarnConfiguration, since there is no way to know what user will
override in yarn-site.xml
Please feel free to correct me.
Thanks
Abhi
> YarnClient.init should ensure that yarn parameters are present
> --------------------------------------------------------------
>
> Key: YARN-855
> URL: https://issues.apache.org/jira/browse/YARN-855
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.0.5-alpha
> Reporter: Siddharth Seth
> Assignee: Abhishek Kapoor
>
> It currently accepts a Configuration object in init and doesn't check whether
> it contains yarn parameters or is a YarnConfiguration. Should either accept
> YarnConfiguration, check existence of parameters or create a
> YarnConfiguration based on the configuration passed to it.
--
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
