Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/16038
Maybe we could have a live talk/chat this evening Paris time / Morning West
Coast time?
If I'm not mistaken both #16037 and this change fix the issue at two
different levels.
* #16037 consider the the is specific to ML and that we can & should work
around it in MLlib
* This change consider the root cause is an inefficiency of treeAggregate
in core whose fix would enable a better fix in MLlib. I updated this PR to
reflect this.
I might have misunderstood your comment
https://github.com/apache/spark/pull/15905#pullrequestreview-8844854
---
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
