storage: fix clone ColumnFile with new page id twice when segmentDangerouslyReplaceDataFromCheckpoint #9436
+6
−47
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.
What problem does this PR solve?
Issue Number: ref #6233
Problem Summary:
What is changed and how it works?
tiflash/dbms/src/Storages/DeltaMerge/DeltaMergeStore_Ingest.cpp
Lines 1042 to 1052 in 9e3ba66
tiflash/dbms/src/Storages/DeltaMerge/Delta/DeltaValueSpace.cpp
Lines 238 to 260 in 9e3ba66
tiflash/dbms/src/Storages/DeltaMerge/Delta/DeltaValueSpace.cpp
Lines 122 to 196 in 9e3ba66
We have acquire new page id in
CloneColumnFilesHelper::clone
, so just reuse the page id inSegment::dangerouslyReplaceDataFromCheckpoint
Check List
Tests
Side effects
Documentation
Release note