GitHub user AnthonyTruchet opened a pull request:
https://github.com/apache/spark/pull/16038
[SPARK-18471][CORE] New treeAggregate overload for big large aggregators
## What changes were proposed in this pull request?
The zero for the aggregation used to be shipped into a closure which is
higly problematic when this zero is big (100s of MB is typical for ML).
This change introduces a new overload of treeAggregate which only ships a
function able to generate this zero.
## How was this patch tested?
Test suite for the core and mllib modules launched locally.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/criteo-forks/spark SPARK-18471
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/16038.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #16038
----
commit f6e23650fcaf943f058494ddd13282f37f9452f5
Author: Anthony Truchet <a.truc...@criteo.com>
Date: 2016-11-17T15:20:19Z
[SPARK-18471][CORE] New treeAggregate overload for big large aggregators
The zero for the aggregation used to be shipped into a closure which is
higly problematic when this zero is big (100s of MB is typical for ML).
This change introduces a new overload of treeAggregate which only ships a
function able to generate this zero.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
