Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/15963
Once more (last time hopefully) I mistakenly fiddled with PR. Closing this
one and replace it with #16037.
Code style review above taken into account in new PR.
---
If your project is
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/15963
Hello @srowen , sorry not to have updated this lately, I've been taken by
other emergencies at work. I'll update this on Monday. Actually I'll submit a
variant of treeAggregate in core that w
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15963
Ping @AnthonyTruchet
---
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,
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/15963
@srowen Here is at last the real PR for SPARK-18471.
Sorry for the noise due to GitHub fiddling...
---
If your project is set up for it, you can reply to this email and have your
re
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15963
Can one of the admins verify this patch?
---
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 feat
