hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-111) JobClient.runJob() should return exit status for a job.
Date Mon, 21 May 2007 17:29:16 GMT

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

Owen O'Malley resolved HADOOP-111.
----------------------------------

       Resolution: Duplicate
    Fix Version/s: 0.13.0

This was fixed by HADOOP-1326.

> JobClient.runJob() should return exit status for a job.
> -------------------------------------------------------
>
>                 Key: HADOOP-111
>                 URL: https://issues.apache.org/jira/browse/HADOOP-111
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Andrzej Bialecki 
>         Assigned To: Owen O'Malley
>             Fix For: 0.13.0
>
>
> JobClient.runJob() doesn't return any values. Any information about the exit status of
a job is discarded (or appears only in logs).
> It should be possible to return the exit status, so that JobClient users can determine
whether a job was successfully completed or not. This is also important when using cmd-line
tools in shell scripts - currently they don't return any exit codes, because it's not possible
to determine the outcome of a job submitted through JobClient. As a consequence, it's difficult
to automate repetitive jobs using shells scripts.
> It would be also nice to have an exit message in case of errors, for human consumption.
> I propose to implement one of the following:
> * change the return type of this method from void to int
> * or, better yet, to put the exit code and optional exit messages inside the JobConf
instance under pre-defined keys.

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


Mime
View raw message