[
https://issues.apache.org/jira/browse/MAPREDUCE-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283578#comment-13283578
]
Robert Vandehey commented on MAPREDUCE-3130:
--------------------------------------------
I'd vote for option #3. Option #2 could have regression issues where someone
depends on a file always being created. Option #1 isn't really a solution just
providing more guidance through documentation. Option #3 is the logical
solution since the expectation is NullOutputFormat is not producing any output
but there is still an expectation of cleaning up after committing.
> Output files are not moved to job output directory after task completion
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-3130
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3130
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: task
> Affects Versions: 0.20.204.0
> Environment: NA
> Reporter: Bhallamudi Venkata Siva Kamesh
>
> When MultipleOutputs (OutputFormat set to TextOutputFormat) is used to write
> output files to different namedOutputFiles, turned off normal output file
> generation(i.e.*part-r-<#reduce>*) by setting OutputFormat as
> NullOutputFormat, task output is not moved to job output directory
> ({color:blue}${mapred.output.dir}{color}).
>
> After the job completion, found output files in
> {color:red}${mapred.output.dir}/_temporary/_attempt-<jobid>-<#reduce>{color}
> (task output directory) rather than in the
> {color:blue}${mapred.output.dir}{color} (job output dir)
--
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
