[CALCITE-7402] Two-level nested correlated subquery causes TopDownGeneralDecorrelator type mismatch during translation#4780
Merged
silundong merged 1 commit intoapache:mainfrom Jan 30, 2026
Conversation
xiedeyantu
approved these changes
Jan 29, 2026
xuzifu666
approved these changes
Jan 30, 2026
silundong
added
the
LGTM-will-merge-soon
…eralDecorrelator type mismatch during translation
|
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-7402
When D-elimination is triggered during decorrelation, outer variables are replaced with local attributes and constrained with
IS_NOT_NULL. The transformation looks like:$0(it's nullable beforeIS_NOT_NULL) will later be used to replace$cor0.DEPTNO(not nullable). The rewrite itself is fine, but the type inference ofFilterdoes not detect the nullability change implied by theIS_NOT_NULLpredicate. That is,$0is still treated as nullable, which leads to a type mismatch when replacing$cor0.DEPTNOlater.