[
https://issues.apache.org/jira/browse/HADOOP-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613928#action_12613928
]
Devaraj Das commented on HADOOP-3150:
-------------------------------------
I am +1 on the approach in the current patch. This patch is an improvement over
what exists in terms of performance.
I am in two minds regarding having an OutputCommitter interface esp. for the
common uses of OutputFormat. So for example, for the FileOutputFormat case, we
have all the logic for committing in the base FileOutputFormat and all the
output formats that deal with FileOutputs inherit that. Although the
sub-classes could override the commit implementation, most of them don't need
to.
Alejandro, could you please enumerate some advantages of having a separate
committer interface vis-a-vis having the commit implementation in a base class
for all related outputformats?
> Move task file promotion into the task
> --------------------------------------
>
> Key: HADOOP-3150
> URL: https://issues.apache.org/jira/browse/HADOOP-3150
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.19.0
>
> Attachments: 3150.patch, patch-3150.txt
>
>
> We need to move the task file promotion from the JobTracker to the Task and
> move it down into the output format.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
