Chris Douglas updated HADOOP-4927:
----------------------------------
Status: Open (was: Patch Available)
This feature doesn't require framework changes, does it? Configuring FileOutputFormat or writing an OutputFormat that lazily creates its files should be sufficient.
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: New Feature
Components: mapred
Reporter: Devaraj Das
Assignee: Jothi Padmanabhan
Fix For: 0.21.0
Attachments: hadoop-4927-v1.patch, hadoop-4927-v2.patch, hadoop-4927.patch
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.
----------------------------------------------------------------------------------------------------------------------------
Key: HADOOP-4927
URL: https://issues.apache.org/jira/browse/HADOOP-4927
Project: Hadoop Core
Issue Type: New Feature
Components: mapred
Reporter: Devaraj Das
Assignee: Jothi Padmanabhan
Fix For: 0.21.0
Attachments: hadoop-4927-v1.patch, hadoop-4927-v2.patch, hadoop-4927.patch
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.