hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-366) Should be able to specify more than one jar into a JobConf file
Date Mon, 28 Aug 2006 20:52:24 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-366?page=comments#action_12431065 ] 
Doug Cutting commented on HADOOP-366:

The rationale for keeping the config file separate from the jar was that folks might use a
single big jar and then submit a sequence of jobs with different parameters, but all of whose
code is in the same jar.  The system could be smart about caching the jar on nodes.  Rebuilding
a jar for each job submitted seemed heavyweight to me.  In fact, that's what this bug was
originally complaining about!

The lib directory is like that in war files.  So it too has a precedent in Java's standards!

> Should be able to specify more than one jar into a JobConf file
> ---------------------------------------------------------------
>                 Key: HADOOP-366
>                 URL: http://issues.apache.org/jira/browse/HADOOP-366
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.4.0
>            Reporter: Thomas FRIOL
> A job should be able to specify more than one jar file into its JobConf file because
sometimes custom Map and Reduce classes or just InputFormat classes uses objects coming from
other jar files. For now, we have to build a unique jar to make Hadoop mapreduce operations

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message