[jira] Updated: (HADOOP-1474) Submittable interface, for the ability to execute and monitor jobs from a java class

["Owen O'Malley (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen O'Malley updated HADOOP-1474:
----------------------------------

    Description: 
Hi,

We wish to add the following interface:
interface Submittable{
           RunningJob submitJob(JobConf jc);
}

Currently there is no clean way to monitor a submitted job programatically, one way would be to call main, and parse the output to figure out Jobid,  and then monitor it using a JobClient.  Currently the only way RunJar can run a Class in a Jar file is using main.invoke(). 

The purpose of this interface is to be able to programatically call the class that extends this interface via another Class (similar to RunJar) and still be able to monitor it like JobClient does.
Essentially, all the functionality within a main class would be encapsulated within this method such as implementing constraints between various user defined job.xml keys.
The purpose of main would be reduced to parsing arguments, setting the JobConf and calling this function.


  was:
Hi,

We wish to add the following interface:
interface Submittable{
           RunningJob submitJob(JobConf jc);
}

Currently there is no clean way to monitor a submitted job programatically, one way would be to call main, and parse the output to figure out Jobid,  and then monitor it using a JobClient.  Currently the only way RunJar can run a Class in a Jar file is using main.invoke(). 

The purpose of this interface is to be able to programatically call the class that extends this interface via another Class (similar to RunJar) and still be able to monitor it like JobClient does.
Essentially, all the functionality within a main class would be encapsulated within this method such as implementing constraints between various user defined job.xml keys.
The purpose of main would be reduced to parsing arguments, setting the JobConf and calling this function.

I discussed this with Milind and Owen and they agreed that such an interface should exist. 



> Submittable interface, for the ability to execute and monitor jobs from a java class
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1474
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1474
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: mapred
>            Reporter: Srikanth Kakani
>
> Hi,
> We wish to add the following interface:
> interface Submittable{
>            RunningJob submitJob(JobConf jc);
> }
> Currently there is no clean way to monitor a submitted job programatically, one way would be to call main, and parse the output to figure out Jobid,  and then monitor it using a JobClient.  Currently the only way RunJar can run a Class in a Jar file is using main.invoke(). 
> The purpose of this interface is to be able to programatically call the class that extends this interface via another Class (similar to RunJar) and still be able to monitor it like JobClient does.
> Essentially, all the functionality within a main class would be encapsulated within this method such as implementing constraints between various user defined job.xml keys.
> The purpose of main would be reduced to parsing arguments, setting the JobConf and calling this function.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.