[
https://issues.apache.org/jira/browse/MAPREDUCE-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved MAPREDUCE-483.
-------------------------------
Resolution: Not A Problem
IMHO, Oozie is the best way to do such workflow stuff. We should close this one
out over Apache Oozie (OOZIE) and given that this has grown stale.
> Enhance 'bin/hadoop job -submit <>'
> -----------------------------------
>
> Key: MAPREDUCE-483
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-483
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Priority: Minor
> Attachments: HADOOP-808_1_20061208.patch, myjob.tgz
>
>
> Today 'bin/hadoop job -submit' takes a config file and just does a
> JobClient.submitJob(jobConf), this isn't flexible enough for cases where the
> user wants to submit a job which calls his main(), does some work and then
> calls 'JobClient.runJob', I propose we enhance this subcommand to handle that
> scenario. This could be really useful for the time we decide to setup a
> simple webpage with 'form' where the user uploads a job.xml & job.jar and we
> can fire the job.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
