Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7334#issuecomment-121094163
Alright, I've updated this to allow the planner to insert the Exchange. We
still can't merge this as-is, though, since it will introduce a bad regression
for the case where Limit is the final operator in a physical plan. AFAIK
there's no easy way to write optimizer rules which reference the parent
operator, so it's hard to write an optimizer rule to recognize this pattern and
use a separate Limit implementation.
---
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]
