hadoop-common-dev mailing list archives

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

James you're right, using a Manifest in the JAR is th standard way of doing this, thanks for
reminding.  And about parameters, we could just pick the right config file in the JAR by passing
a JVM argument:

  java -Dconfig=mybigcluster -jar mapred.jar

Or even using command-line arguments:

  java -jar mapred.jar mybigcluster

> 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

        

Mime
View raw message