br: handle the merged SST response

Leavrth commented 1 day ago

What problem does this PR solve?

Issue Number: close #57389

Problem Summary: the backup merge data from different key ranges into one SST file, so BR needs to be able to handle its response.

What changed and how does it work?

handle the merged SST response.

Check List

Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test
- [ ] I checked and no code files have been changed.

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

ti-chi-bot[bot] commented 1 day ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from leavrth, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/pingcap/tidb/blob/master/OWNERS)** - **[br/OWNERS](https://github.com/pingcap/tidb/blob/master/br/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

tiprow[bot] commented 1 day ago

Hi @Leavrth. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

ti-chi-bot[bot] commented 1 day ago

@Leavrth: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev_2	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test check-dev2`
idc-jenkins-ci-tidb/mysql-test	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test mysql-test`
idc-jenkins-ci-tidb/unit-test	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test unit-test`
idc-jenkins-ci-tidb/check_dev	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test check-dev`
pull-integration-ddl-test	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test pull-integration-ddl-test`
pull-br-integration-test	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test pull-br-integration-test`
pull-integration-e2e-test	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test pull-integration-e2e-test`
pull-mysql-client-test	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test pull-mysql-client-test`
idc-jenkins-ci-tidb/build	a5b92cf306fe4a1a5b57debceb1c3103c77e9a90	link	true	`/test build`

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

pingcap / tidb