-
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
lightning: save NEXT_GLOBAL_ROW_ID as uint64 instead of int64 (#45614) #45944
lightning: save NEXT_GLOBAL_ROW_ID as uint64 instead of int64 (#45614) #45944
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-6.5 #45944 +/- ##
================================================
Coverage ? 74.2405%
================================================
Files ? 1083
Lines ? 351118
Branches ? 0
================================================
Hits ? 260672
Misses ? 74076
Partials ? 16370 |
[LGTM Timeline notifier]Timeline:
|
/cc @lance6716 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: D3Hunter, lance6716 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is an automated cherry-pick of #45614
What problem does this PR solve?
Issue Number: close #45427
Problem Summary:
lightning wrongly use
int64
to saveNEXT_GLOBAL_ROW_ID
.pingcap/tiflow#9391 (comment)
What is changed and how it works?
https://github.com/pingcap/tidb/blob/f1b9da103166162944ae41dc0943c93c0b91923b/br/pkg/lightning/backend/tidb/tidb.go#L847C1-L852
nextID
's type is changed tostring
.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.