[
https://issues.apache.org/jira/browse/MAPREDUCE-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved MAPREDUCE-4694.
--------------------------------
Resolution: Won't Fix
Assignee: (was: Harsh J)
This bug's existed for over 5 years now. I've not seen new complaints/interest
in unifying the behaviour. Closing out as expected behaviour.
> Inconsistency in reduce input record counters between the stable and evolving
> APIs
> ----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4694
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4694
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 2.0.0-alpha
> Reporter: Harsh J
> Labels: inconsistency, regression, test
> Attachments: MAPREDUCE-4694.patch, MAPREDUCE-4694.patch
>
>
> In the stable (mapred) API execution, if the values iterator is skipped by a
> user, the records underneath it aren't counted in the "Reduce input records"
> counter as the key progresses to the next unique one. In the evolving API
> (mapreduce) API execution, if the values iterator is skipped by a user, the
> records underneath it is still counted as the key progresses to the next
> unique one.
> This behavior comes to me as a faulty one in the old API. A "Reduce input
> records" counter must always define all the records that have been passed
> into a reducer (cause they are read regardless of skipping), and both API's
> record counting despite user applications must be consistent.
> I'll post a test case illustrating this shortly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
