[CALCITE-7457] VALUES and SELECT produce different validation results for the same expression#4858
Open
dssysolyatin wants to merge 1 commit intoapache:mainfrom
Open
Conversation
…on results for the same expression
dssysolyatin
changed the title
|
caicancai
approved these changes
Apr 2, 2026
dssysolyatin
added
the
LGTM-will-merge-soon
xiedeyantu
reviewed
Apr 3, 2026
|
|
||
| /** Test case for | ||
| * <a href="https://issues.apache.org/jira/browse/CALCITE-7457">[CALCITE-7457] | ||
| * Top-level VALUES and SELECT produce different validation results |
Member
There was a problem hiding this comment.
The javadoc should be removed "Top-level"?
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.
Jira Link
CALCITE-7457
Changes Proposed
VALUESnow routes throughvalidateQuery, triggeringTableConstructorNamespace.validateImplvalidation (which callsvalidateValuesandinferUnknownTypes). The fix is a validateCall override in SqlValuesOperator.inferUnknownTypesno longer descends into subqueries (node.isA(SqlKind.QUERY)). Each query handles its owninferUnknownTypesduring its own validation.SELECTandVALUESbehaves the same way