[
https://issues.apache.org/jira/browse/YARN-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-1748:
------------------------------------------
Assignee: Vinod Kumar Vavilapalli
We need those conf files for YARN tests themselves. I can see why downstream
projects can break. I think the real problem is that MiniYARNCluster is under a
test jar (under src/tests). I think that moving class to regular code
(src/java) will avoid this.
IOW, downstream projects will need to start depending on
hadoop-yarn-server-tests-2.3.0.jar instead of
hadoop-yarn-server-tests-2.3.0-tests.jar if we change that. At which point
whether we have core-site in our test code or not shouldn't matter.
This is kind of an incompatible change w.r.t jar dependencies. I'd like to
gather opinions before we do this.
> hadoop-yarn-server-tests packages core-site.xml breaking downstream tests
> -------------------------------------------------------------------------
>
> Key: YARN-1748
> URL: https://issues.apache.org/jira/browse/YARN-1748
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Sravya Tirukkovalur
> Assignee: Vinod Kumar Vavilapalli
>
> Jars should not package config files, as this might come into the classpaths
> of clients causing the clients to break.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
