-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
function result name should contain collator info (#2808) #3018
function result name should contain collator info (#2808) #3018
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/merge |
@JaySon-Huang: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
This pull request has been accepted and is ready to merge. Commit hash: d5ba8cb
|
/run-all-tests |
/merge |
@JaySon-Huang: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/merge |
@JaySon-Huang: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/run-all-tests |
This is an automated cherry-pick of #2808
What problem does this PR solve?
Issue Number: close #2793
Problem Summary:
As the issue described.
What is changed and how it works?
Proposal: xxx
What's Changed:
The root cause is, the join other condition of query is
eq(test.t1.col_varchar_20_key_signed, test.t2.col_char_20_key_signed) with ci collator
and
not(in(test.t1.col_varchar_20_key_signed, test.t1.col_varbinary_20_key_signed, test.t1.col_varbinary_20_undef_signed, test.t2.col_varchar_20_undef_signed, test.t2.col_char_20_key_signed)) with bin collator
And for patterns like
col in (col_1, col_2)
, since TiFlash does not support this directly, it will be rewritten tocol = col_1 or col = col_2
, so in TiFlash, the join other condition is actually:eq(test.t1.col_varchar_20_key_signed, test.t2.col_char_20_key_signed) with ci collator
and
not (eq(test.t1.col_varchar_20_key_signed, test.t1.col_varbinary_20_key_signed) with bin collator or eq(test.t1.col_varchar_20_key_signed, test.t1.col_varbinary_20_undef_signed) with bin collator or eq(test.t1.col_varchar_20_key_signed, test.t2.col_varchar_20_undef_signed) with bin collator or eq(test.t1.col_varchar_20_key_signed, test.t2.col_char_20_key_signed) with bin collator))
And in TiFlash, if a function is already calucated, it will try to reuse the result to avoid redundancy calculation, and the result name for a function is generated by
genFuncString
, it just concat the function name and all its arguments' name, foreq(test.t1.col_varchar_20_key_signed, test.t2.col_char_20_key_signed) with ci collator
andeq(test.t1.col_varchar_20_key_signed, test.t2.col_char_20_key_signed) with bin collator
, they will have the same result name, so only one of them will be executed, and the other will result the result, this will clearly cause a collation related bug.This pr add collation related info in
genFuncString
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests
Side effects
Release note