You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/24 02:08:45 UTC

[jira] [Resolved] (MAPREDUCE-1005) why should not capacity sheduler jar not copied under lib during build

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

Allen Wittenauer resolved MAPREDUCE-1005.
-----------------------------------------

    Resolution: Fixed

Fixed in Hadoop 2.x

> why should not capacity sheduler jar not copied under lib during build
> ----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1005
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1005
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.21.0
>            Reporter: Iyappan Srinivasan
>
> Right now, the capacity-scheduler.jar is not getting copied under trunk/build/hadoop-mapred-0.21.0-dev/lib/. It stays in trunk/build/hadoop-mapred-0.21.0-dev/contrib/capacity-scheduler/hadoop-0.21.0-dev-capacity-scheduler.jar.  Every time somebody tries to build the trunk, they have to copy this jar from contrib to lib manually. 
> During any kind of build (ant binary, ant bin-package, ant package) , this jar file should also get copied to lib. If a person uses default or fair sheduler, he will not use it, but still there is no harm of it being in lib. If he uses capacity scheduler, then it gets used automatically. This manual copy should be avoided.



--
This message was sent by Atlassian JIRA
(v6.2#6252)