[
https://issues.apache.org/jira/browse/HADOOP-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658602#action_12658602
]
Doug Cutting commented on HADOOP-4927:
--------------------------------------
I'm not convinced this is a bug. If you specify N output partitions then you
should generate N output files, even if some of them are empty, no? One could
write an OutputFormat that lazily creates its output files, but that's not the
contract of FileOutputFormat.
> Part files on the output filesystem are created irrespective of whether the
> corresponding task has anything to write there
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4927
> URL: https://issues.apache.org/jira/browse/HADOOP-4927
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Devaraj Das
> Fix For: 0.20.0
>
>
> When OutputFormat.getRecordWriter is invoked, a part file is created on the
> output filesystem. But the created RecordWriter is not used until the
> OutputCollector.collect call is made by the task (user's code). This results
> in empty part files even if the OutputCollector.collect is never invoked by
> the corresponding tasks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
