Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10896#issuecomment-182169168
I probably will not be able to take a close look on this PR until later
this month. I have a question regarding the approach of PR. Right now, we
always plan partial aggregation operators first (in SparkStrategies) and then
add Exchange operators (in EnsureRequirements). Another approach will be that
we do not add partial aggregation operators in SparkStrategies. Then, after we
figure out where we need exchange operators, we add partial aggregation
operators. This approach probably needs more code changes. But, I feel it is a
more cleaner approach.
@maropu @marmbrus what do you think?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]