You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "He Tianyi (JIRA)" <ji...@apache.org> on 2016/08/16 02:49:20 UTC
[jira] [Created] (MAPREDUCE-6755) Report correct spill/output size
for map in nativetask
He Tianyi created MAPREDUCE-6755:
------------------------------------
Summary: Report correct spill/output size for map in nativetask
Key: MAPREDUCE-6755
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6755
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: nativetask
Affects Versions: 2.6.0
Reporter: He Tianyi
Priority: Minor
Currently nativetask always report '-1' as size when calling methods in {{MapOutputFile}}.
This is an obstacle for custom {{MapOutputFile}} implementations where size matters (e.g. determine which disk to use).
The issue propose to estimate spill/output/index size in nativetask like java implementation does.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org