Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10689#issuecomment-170473951
@gatorsmile the fix looks good.
@rxin / @marmbrus / @gatorsmile I am not sure if we should support this at
all. Using a limit in SELECT's connected by a UNION ALL is fine, but things
tend to get really strange once you start using this in combination with other
SET or JOIN operations; it'll get very hard to reasion about the result. Most
RDMS'es do not support this. I'd rather have an optimizer rule which pushes
down limit clauses whenever this is possible.
---
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]
