hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira AJISAKA (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3958) TestYarnConfigurationFields should be moved to hadoop-yarn-api module
Date Mon, 27 Jul 2015 02:44:05 GMT

     [ https://issues.apache.org/jira/browse/YARN-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Akira AJISAKA updated YARN-3958:
--------------------------------
    Hadoop Flags: Reviewed
         Summary: TestYarnConfigurationFields should be moved to hadoop-yarn-api module  (was:
TestYarnConfigurationFields should be moved to hadoop-yarn-api)

> TestYarnConfigurationFields should be moved to hadoop-yarn-api module
> ---------------------------------------------------------------------
>
>                 Key: YARN-3958
>                 URL: https://issues.apache.org/jira/browse/YARN-3958
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>         Attachments: YARN-3958.01.patch, YARN-3958.02.patch, YARN-3958.03.patch
>
>
> Currently TestYarnConfigurationFields is present in hadoop-yarn-common. The test is for
checking whether all the configurations declared in YarnConfiguration exist in yarn-default.xml
or not.
> But as YarnConfiguration is in hadoop-yarn-api, if somebody changes this file, it is
not necessary that this test will be run. So if the developer misses to update yarn-default.xml
and patch is committed, it will lead to unnecessary test failures after commit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message