-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Subquery support #2248
Labels
enhancement
New feature or request
Comments
This was referenced Apr 25, 2022
Some additional ideas for subquery optimizations:
More generally, one can attempt this approach, which is a lot less messy than relying on countless rewriting heuristics (which is also highly error-prone): |
This was referenced Mar 5, 2023
I filed #5483 to track the few items that are not done yet, and am going to close this ticket as we have subquery support in DataFusion now 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
We have many issues now for subquery support, with some duplication so I thought it would be good to create one epic to track all of this work.
There is also a design document.
Logical Plan
LogicalPlan::TableScan
should not depend on the physical plan #2247Query
for datafusion #2181Expr::InSubquery
andExpr::ScalarSubquery
#2342SQL Query Planner
Logical Plan Optimizations
IN
subqueries by rewriting as semi join #488Physical Plan
Ballista
The text was updated successfully, but these errors were encountered: