hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-3675) A job must not be submitted when there are no mappers to run
Date Mon, 16 Jan 2012 19:39:40 GMT

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

Arun C Murthy resolved MAPREDUCE-3675.

          Resolution: Invalid
    Target Version/s: 0.23.1, 0.24.0, 1.1.0, 0.22.1  (was: 0.22.1, 1.1.0, 0.24.0, 0.23.1)

Agree with Vinod.

Oozie workflows with such jobs is a particularly important use-case for this 'feature'.
> A job must not be submitted when there are no mappers to run
> ------------------------------------------------------------
>                 Key: MAPREDUCE-3675
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3675
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.0.0
>            Reporter: Harsh J
>            Priority: Minor
> Right now, one's able to run a job with an empty input directory and a job is indeed
> The job runs no mappers, but any number of specified reducers are run anyway as dummy
> This should be/could be avoided. I do not see a use for such an allowance, and it looks
mostly like a logic slip to me with empty arrays involved and accepted.
> The fix could be simply in the job submission code, where we can avoid submitting if
the splits are nil.

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


View raw message