Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
2.6.0
-
None
-
None
Description
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.