-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
types/json: fix JSON comparison for int and float (#17622) #17715
types/json: fix JSON comparison for int and float (#17622) #17715
Conversation
Signed-off-by: sre-bot <sre-bot@pingcap.com>
/run-all-tests |
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
@qw4990,Thanks for you review. |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@sre-bot merge failed. |
/run-all-tests |
/run-integration-common-test |
/run-unit-test |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
cherry-pick #17622 to release-3.0
What problem does this PR solve?
Issue Number: close #16267
Problem Summary:
Compare between large BIGINTs may got unexpected results.
What is changed and how it works?
Proposal: xxx
What's Changed:
How it Works:
Related changes
pingcap/docs
/pingcap/docs-cn
:pingcap/tidb-ansible
:Check List
Tests
Release note