[ 
https://issues.apache.org/jira/browse/HADOOP-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710701#action_12710701
 ] 

Vinod K V commented on HADOOP-5850:
-----------------------------------

ant test-patch results:
{code}
     [exec] +1 overall.
     [exec]
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]
     [exec]     +1 tests included.  The patch appears to include 6 new or 
modified tests.
     [exec]
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec]
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec]
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
     [exec]
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath 
integrity.
     [exec]
     [exec]     +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
     [exec]
     [exec]
     [exec]
     [exec]
     [exec] 
======================================================================
     [exec] 
======================================================================
     [exec]     Finished build.
     [exec] 
======================================================================
     [exec] 
======================================================================
{code}

> map/reduce doesn't run jobs with 0 maps
> ---------------------------------------
>
>                 Key: HADOOP-5850
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5850
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.20.0
>            Reporter: Owen O'Malley
>            Assignee: Vinod K V
>            Priority: Critical
>             Fix For: 0.20.1
>
>         Attachments: HADOOP-5850-20090519.1.txt, HADOOP-5850-20090519.txt
>
>
> Currently, the framework ignores jobs that have 0 maps. This is incorrect. 
> Many pipelines need the job to run (if nothing else, to create the output 
> directory!) so that subsequent jobs don't fail. Effectively, there will be no 
> map tasks and the reduce tasks should immediately set up the Reducer and 
> RecordWriter and then call close on both since there are no inputs to the 
> reduce. I believe it should just work if we remove the check...

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

Reply via email to