[ http://issues.apache.org/jira/browse/HADOOP-31?page=comments#action_12365807 ]
Owen O'Malley commented on HADOOP-31: ------------------------------------- I would argue that rather than creating more framework, you just use the arguments and dispatch on the first argument. If you need something generic you could do something like I did with the ExampleDriver. > 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: [EMAIL PROTECTED] > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
