[ http://issues.apache.org/jira/browse/HADOOP-366?page=comments#action_12421664 ] Thomas FRIOL commented on HADOOP-366: -------------------------------------
Owen, I think you did not understand correctly my explanations. I will try to be more precise. In fact, when I am writting a new job using a jobConf.xml file, I am able to define a custom jar using the property 'mapred.jar'. This jar is the uploaded to the DFS and then appended to the Hadoop classpath of each task tracker. The exact purpose of my problem is that today, we can specify only one jar and I think it could be great to be able to specify a comma separated list of jars so that we do not have to build a single jar with differents existing jars to give it to each Hadoop task tracker. Am I more precise now ? Thanks for your help. > 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
