Resolve type mismatch when WHEN result type differs from ELSE (INT32 vs INT64)#17415
Merged
JackieTien97 merged 5 commits intomasterfrom Apr 3, 2026
Merged
Resolve type mismatch when WHEN result type differs from ELSE (INT32 vs INT64)#17415JackieTien97 merged 5 commits intomasterfrom
JackieTien97 merged 5 commits intomasterfrom
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #17415 +/- ##
==========================================
Coverage 39.75% 39.75%
Complexity 312 312
==========================================
Files 5134 5135 +1
Lines 346874 346986 +112
Branches 44186 44209 +23
==========================================
+ Hits 137906 137952 +46
- Misses 208968 209034 +66 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…lational/it/query/recent/copyto/IoTDBCopyToTsFileIT.java
|
JackieTien97
approved these changes
Apr 3, 2026
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
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.



Description
When executing:
SELECT if(col_int64>0, col_int64,cast(0 as int64)) FROM test.if_test;
In table model, if(...) is converted to SearchedCaseExpression. During type analysis:
WHEN clause result type is inferred as INT64 (from col_int64)
ELSE clause cast(0 as int64) has internal LongLiteral(0) inferred as INT32 (since 0 is within Integer range)
This causes visitSearchedCaseExpression to throw:
Default result type must be the same as WHEN result types: INT32 vs INT64