[
https://issues.apache.org/jira/browse/MAPREDUCE-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143118#comment-13143118
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3215:
----------------------------------------------------
Test with the commented out code reenabled fails without the patch, and passes
with the patch.
Patch looks good too. +1.
I think we should deprecate the setJobSetupCleanupNeeded() API. Before 0.23, we
could disable set up and cleanup, yet obtain the output when using
FileOutputCommitter in the job-output directory. But post 0.23.0, that won't be
the case because of the nested temporary directories to support AM
recoverability. Will open a separate ticket.
> org.apache.hadoop.mapreduce.TestNoJobSetupCleanup failing on trunk
> ------------------------------------------------------------------
>
> Key: MAPREDUCE-3215
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3215
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Priority: Minor
> Fix For: 0.24.0
>
> Attachments: MR-3215.1.patch
>
>
> Testcase: testNoJobSetupCleanup took 13.271 sec
> FAILED
> Number of part-files is 0 and not 1
> junit.framework.AssertionFailedError: Number of part-files is 0 and not 1
> at
> org.apache.hadoop.mapreduce.TestNoJobSetupCleanup.submitAndValidateJob(TestNoJobSetupCleanup.java:60)
> at
> org.apache.hadoop.mapreduce.TestNoJobSetupCleanup.testNoJobSetupCleanup(TestNoJobSetupCleanup.java:70)
--
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