hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-855) YarnClient.init should ensure that yarn parameters are present
Date Thu, 01 Aug 2013 02:15:48 GMT

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

Siddharth Seth commented on YARN-855:
-------------------------------------

The simplest would be to check the configuration type - which keeps the API stable.

The reason I mentioned parameters is that apps that use YarnClient may have their own configuration
type - e.g. JobConf or a HiveConf. Type information ends up getting lost even if these apps
have created their configurations based on a YarnConfiguration.
                
> 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

Mime
View raw message