[
https://issues.apache.org/jira/browse/MAPREDUCE-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308129#comment-14308129
]
Jason Lowe commented on MAPREDUCE-5847:
---------------------------------------
bq. Incompatible changes can go into trunk.
Understood, but I'm arguing we shouldn't break incompatibility without
sufficient merit. Each incompatibility instance is a hurdle someone needs to
jump to move from Hadoop 2.x to Hadoop 3.x. Hence I'm wondering if others feel
this is worth adding another hurdle or not.
> Remove redundant code for fileOutputByteCounter in MapTask and ReduceTask
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-5847
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5847
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv1, mrv2, task
> Affects Versions: 2.4.0
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: MAPREDUCE-5847.v01.patch, MAPREDUCE-5847.v02.patch
>
>
> Both MapTask and ReduceTask carry redundant code to update BYTES_WRITTEN
> counter. However, {{Task.updateCounters}} uses file system stats for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
