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: duplicate resolution support to use DELETE to cleanup clustered table #44799
Conversation
Signed-off-by: lance6716 <lance6716@gmail.com>
/run-integration-br-test |
/run-integration-br-test |
Signed-off-by: lance6716 <lance6716@gmail.com>
/test tiprow_fast_test |
@hawkingrei: The specified target(s) for
Use
In response to this:
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 kubernetes/test-infra repository. |
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.
rest lgtm
|
||
var buffer []types.Datum | ||
var indexBuffer []byte | ||
for _, index := range indices { | ||
// skip clustered PK | ||
if index.Meta().Primary && isCommonHandle { |
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.
should we skip clustered & single-int column
kind of pk?
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.
added test 7338cc1
When PKIsHandle (test file line 83), I remember the PK will not appear in indices
, so no need to skip it.
Signed-off-by: lance6716 <lance6716@gmail.com>
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: D3Hunter, GMHDBJD 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 |
/retest |
/run-integration-br-test |
@lance6716: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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 kubernetes/test-infra repository. |
/ok-to-test |
What problem does this PR solve?
Issue Number: ref #44723
Problem Summary:
What is changed and how it works?
The fix is made at TiKV side tikv/tikv#14960
this PR fix a bug that clustered PK will generate non-clustered PK index KV and be deleted when resolve duplication
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.