hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4931) Add user-APIs for classpath precedence control
Date Thu, 10 Jan 2013 19:36:12 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549970#comment-13549970

Steve Loughran commented on MAPREDUCE-4931:

I thought we were moving away from a JobConf with many, may helper methods to just conf.get/set?
> 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 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

View raw message