[
https://issues.apache.org/jira/browse/MAPREDUCE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved MAPREDUCE-4931.
--------------------------------
Resolution: Not a Problem
Target Version/s: (was: 3.0.0)
Closing out as Not A Problem, given the classloader approaches in MR2 and also
Steve's comment earlier.
> Add user-APIs for classpath precedence control
> ----------------------------------------------
>
> Key: MAPREDUCE-4931
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4931
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Affects Versions: 1.0.0
> Reporter: Harsh J
> Priority: Minor
>
> The feature config from MAPREDUCE-1938 of allowing tasks to start with
> user-classes-first is fairly popular and can use its own API hooks in
> Job/JobConf classes, making it easier to discover and use it rather than
> continuing to keep it as an advanced param.
> I propose to add two APIs to Job/JobConf:
> {code}
> void setUserClassesTakesPrecedence(boolean)
> boolean userClassesTakesPrecedence()
> {code}
> Both of which, depending on their branch of commit, set the property
> {{mapreduce.user.classpath.first}} (1.x) or
> {{mapreduce.job.user.classpath.first}} (trunk, 2.x and if needed, in 0.23.x).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
