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 "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2013/02/08 03:39:13 UTC

[jira] [Commented] (MAPREDUCE-4931) Add user-APIs for classpath precedence control

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

Karthik Kambatla commented on MAPREDUCE-4931:
---------------------------------------------

[~stevel@apache.org], makes sense to start that discussion soon, now that discussions of a beta release in the "near"-future have come up. :)
                
> 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