Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/16037
@sethah Agreed, that's why I uggested to add a dedicated treeAggregate
wrapper to MLlin Utils which would take care of that without fiddling with
sparsity for each seqOP and comboOp. See closed #16078 for the idea...
---
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
