lightning: fix gcs max key limit (#30393)#30561
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
|
/run-all-tests |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: a59e1fa |
|
@3pointer The release-5.2 branch CI is broken.. |
|
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/4fb684d5d9c9848e7ee585bb1a1c0cdb9a2e75ed |
cherry-pick #30393 to release-5.2
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/30561After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #30377
Problem Summary:
opt.ListCountis the number of keys fetched each time for s3, instead of the limitation.What is changed and how it works?
ignore
opt.ListCountin gcs and directly walk all the keys.Check List
Tests
Side effects
Documentation
Release note