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] Resolved: (HADOOP-31) Stipulate main class in a job jar when using 'hadoop jar JARNAME'
Date Fri, 10 Feb 2006 16:31:56 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-31?page=all ]
Doug Cutting resolved HADOOP-31:

    Resolution: Won't Fix

Closing at  reporter's request.

> Stipulate main class in a job jar when using 'hadoop jar JARNAME'
> -----------------------------------------------------------------
>          Key: HADOOP-31
>          URL: http://issues.apache.org/jira/browse/HADOOP-31
>      Project: Hadoop
>         Type: New Feature
>     Reporter: stack@archive.org
>     Priority: Minor

> One use case I forsee is building one jar but using this one jar running multiple jobs:
E.g. A single nutch job jar would now be used to do indexing job, later same jar is used to
do dedup, etc. Currently, the recently added hadoop 'jar' option just takes the jar name then
looks in the jar MANIFEST.MF for the Main-Class, failing if not present. This is grand but
for the scenario above, it means I have to create a jar per job I want to run -- each with
a different MANIFEST.MF#Main-Class entry. 
> Can we pass the Main-Class on the hadoop command-line as an (optional) argument to 'hadoop
jar JAR_NAME'? (I can make a patch if wanted). 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message