Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/12306#issuecomment-210167691
@davies I do agree that it is better to do the rewriting later on. I don't
think SQL generation is too much of a problem, since semi and anti joins are
supported by SQL generation.
The analyzer should produce a `LogicalPlan` which can directly be planned.
By moving the rewrite into the Optimizer we would violate this, by having
EXISTS and IN subquery expressions arround together with inverted attribute
references. So I am not super excited about moving this into the optimizer, but
I am keeping an open mind... :)
---
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]
