-
Notifications
You must be signed in to change notification settings - Fork 1.9k
feat: Support planning subqueries with OuterReferenceColumn belongs to non-adjacent outer relations
#18806
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
Open
duongcongtoai
wants to merge
10
commits into
apache:main
Choose a base branch
from
duongcongtoai:plann-recursive-subquery
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+242
−61
Open
feat: Support planning subqueries with OuterReferenceColumn belongs to non-adjacent outer relations
#18806
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
2a828ed
fix: allow OuterRefColumn for non-adjacent outer relation
duongcongtoai dea0b70
fix: accidentally pushdown filter with subquery
duongcongtoai 5ed2d24
chore: clippy
duongcongtoai c2caf37
chore: rm debug details
duongcongtoai cec566a
fix: breaking changes
duongcongtoai 699424d
fix: lateral join losing its outer ref columns
duongcongtoai 4edaf61
test: more test case for other decorrelation
duongcongtoai 244a778
doc: better comments
duongcongtoai 18f203d
Merge remote-tracking branch 'origin/main' into plann-recursive-subquery
duongcongtoai 8a8da40
fix: test
duongcongtoai File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do think this is the key change -- that rather than having a single outer query schema, we need to have a stack, one for each in the relation.
However it seems like we shouldn't need both
outer_query_schemaas well a stack of them -- outer_query_schemas should always be enough -- maybe you can addpushandpopmethods that add/remove from the schema stackOne thought I had while looking at this PR is that a more logical structure would be for each PlannerContext to have a reference to its parent -- something like
And remove the explicit
outer_query_schema