[ http://issues.apache.org/jira/browse/HADOOP-366?page=comments#action_12431013 ] James P. White commented on HADOOP-366: ---------------------------------------
I didn't finish that thought... I also don't think jobs should have this "external-config-file-plus-jar-file" structure. The job should just be a jar file and the configuration contained within it. There are several ways to do that. The one that is the least change to the current implementation is to simply put the JobConf file (sans the mapred.jar property) in the root of the jar file. Putting a suitable property in the manifest to tag the jar as a Hadoop job file is a good idea too, although it then opens the question of what other properties might belong there as well. > 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 works. -- 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
