Storage: Adapt to ingesting snapshot with irregular region range (release-7.5)#10153
Conversation
Signed-off-by: JaySon-Huang <tshent@qq.com>
Signed-off-by: JaySon-Huang <tshent@qq.com>
Signed-off-by: JaySon-Huang <tshent@qq.com>
Signed-off-by: JaySon-Huang <tshent@qq.com>
Signed-off-by: JaySon-Huang <tshent@qq.com>
|
/retest |
Signed-off-by: JaySon-Huang <tshent@qq.com>
e81a716 to
7f32645
Compare
Signed-off-by: JaySon-Huang <tshent@qq.com>
|
@JaySon-Huang: You cannot manually add or delete the cherry pick branch category labels. It will be added automatically by bot when the PR is created. DetailsIn response to adding label named type/cherry-pick-for-release-7.5. 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. |
Signed-off-by: JaySon-Huang <tshent@qq.com>
fd10be7 to
da952fd
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JinheLin, Lloyd-Pottiger The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
…ease-7.5) (pingcap#10153) close pingcap#10147 Storage: Adapt to ingesting snapshot with irregular region range If the key format is "t${tableID}_r${handleID1}{AnySuffix}", and `AnySuffix` is not empty, `"t${tableID}_r${handleID1}{AnySuffix}" > "t${tableID}_r${handleID1}"` according to the the comparison semantics of "Key" on TiDB/TiKV. For example, If a table is non-clustered, that is with Int64 as the HandleID type. And the range of a Region is `["xxx_r{handleId1}{AnySuffix}", "xxx_r{handleId2}{AnySuffix}")`, where handleId1 = 100, handleId2 = 200. If `AnySuffix` is empty, then Region contains the left-closed-right-open range of `[handleID1, handleID2)` If `AnySuffix` is not empty, then Region contains the range `(handleID1, handleID2]`, which is actually the left-closed-right-open range of `[handleID1+1, handleID2+1)`. Signed-off-by: JaySon-Huang <tshent@qq.com>
cherry-pick of #10151
What problem does this PR solve?
Issue Number: close #10147
Problem Summary: As the issue describe
What is changed and how it works?
RowKeyValue(bool is_common_handle_, HandleValuePtr value_)toRowKeyValue::fromHandleWithSuffix(bool is_common_handle_, HandleValuePtr value_)RowKeyValueto parsingRowKeyRange::fromRegionRangeCheck List
Tests
Side effects
Documentation
Release note