[CALCITE-7401] Multi-level correlated subqueries cause an out-of-range error in the TopDownGeneralDecorrelator#4777
Merged
silundong merged 1 commit intoapache:mainfrom Jan 29, 2026
Conversation
xiedeyantu
approved these changes
Jan 28, 2026
mihaibudiu
reviewed
Jan 28, 2026
| CoreRules.FILTER_CORRELATE)) | ||
| .build(); | ||
| HepPlanner prePlanner = new HepPlanner(preProgram); | ||
| HepPlanner prePlanner = |
Contributor
There was a problem hiding this comment.
this deserves a comment about the DAG stuff; the PR description would be fine here.
mihaibudiu
approved these changes
Jan 29, 2026
…e error in the TopDownGeneralDecorrelator
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
CALCITE-7401
The root cause of this issue is that the
TopDownGeneralDecorrelatoruses aHepPlannerwhichnoDagis FALSE during the preprocessing phase before decorrelation, which causes equivalent nodes to share the same object. In scenarios with nested correlations, equivalent nodes at different nesting levels bind to different outer variables and therefore have different decorrelation information (UnnestedQuery). Since these nodes share the same object, this leads to corrupted records inmapRelToUnnestedQuery.