Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/17000
Hi @ZunwenYou Do you know what's the reason that treeAggregate failed when
feature dimension reach 20 million?
I think this potentially can help with the 2G disk shuffle spill limit. (to
be verified).
Also we should evaluate the memory consumption due to the slice and copy.
---
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
