[
https://issues.apache.org/jira/browse/MAPREDUCE-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated MAPREDUCE-1073:
-------------------------------------------
Status: Open (was: Patch Available)
Canceling the patch as the latest patch is over a year old, and will not apply
to trunk any more. Dick, if you are still interested in getting this patch in,
please up merge and repost it. I would be happy to review it, give you feed
back on your approach, and commit it for you. If you have abandoned the JIRA
please post a comment in the JIRA so I can close it for you.
> Progress reported for pipes tasks is incorrect.
> -----------------------------------------------
>
> Key: MAPREDUCE-1073
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1073
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: pipes
> Affects Versions: 0.20.1
> Reporter: Sreekanth Ramakrishnan
> Assignee: Dick King
> Attachments: MAPREDUCE-1073--yhadoop20--2010-07-22--1530.patch,
> MAPREDUCE-1073--yhadoop20--2010-07-22.patch, MAPREDUCE-1073_yhadoop20.patch,
> mapreduce-1073--2010-03-31.patch, mapreduce-1073--2010-04-06.patch
>
>
> Currently in pipes,
> {{org.apache.hadoop.mapred.pipes.PipesMapRunner.run(RecordReader<K1, V1>,
> OutputCollector<K2, V2>, Reporter)}} we do the following:
> {code}
> while (input.next(key, value)) {
> downlink.mapItem(key, value);
> if(skipping) {
> downlink.flush();
> }
> }
> {code}
> This would result in consumption of all the records for current task and
> taking task progress to 100% whereas the actual pipes application would be
> trailing behind.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
