fix string coercion missing in Eq/NotEq operator#2258
Merged
yjshen merged 2 commits intoapache:masterfrom Apr 18, 2022
Merged
Conversation
WinkerDu
changed the title
Contributor
Author
|
cc @alamb @xudong963 @liukun4515 @yjshen, please have a review, thank you. |
xudong963
approved these changes
Apr 18, 2022
yjshen
approved these changes
Apr 18, 2022
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
5 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.
Which issue does this PR close?
Closes #2225.
Rationale for this change
Suppose
large_stringis aDataType::LargeUtf8column in tablet, sql likewill throw an error:
Plan("'LargeUtf8 = Utf8' can't be evaluated because there isn't a common type to coerce the types to")This pr fix it.
What changes are included in this PR?
Introduce
string_coerciontocomparison_eq_coercionAre there any user-facing changes?
No.