[
https://issues.apache.org/jira/browse/MAPREDUCE-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188098#comment-13188098
]
Harsh J commented on MAPREDUCE-3675:
------------------------------------
Thanks Alejandro, for clarifying on Oozie.
Vinod's use cases, however unorthodox-looking, would be reason enough we
shouldn't break this.
Not that it causes any major issues (apart from temporary slot soakups, maybe).
> 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 scheduled.
> The job runs no mappers, but any number of specified reducers are run anyway
> as dummy tasks.
> 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
