-
Notifications
You must be signed in to change notification settings - Fork 709
[CORE-15023]: Cloud Storage Clients: Implement batch delete for GCS #29144
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
[CORE-15023]: Cloud Storage Clients: Implement batch delete for GCS #29144
Conversation
9140138 to
00a459a
Compare
|
/ci-repeat 1 |
|
/cdt |
|
/cdt |
|
/cdt |
a244702 to
146cf30
Compare
|
/cdt |
146cf30 to
813a915
Compare
|
/cdt |
813a915 to
0ca9a5a
Compare
|
/ci-repeat 1 |
|
/cdt |
0ca9a5a to
a5cf5a4
Compare
|
/cdt |
1 similar comment
|
/cdt |
600e6ee to
aab0bcd
Compare
|
/cdt |
2 similar comments
|
/cdt |
|
/cdt |
99758a3 to
8453fb8
Compare
|
/cdt |
|
/cdt |
…ndler Signed-off-by: Oren Leiman <[email protected]>
Signed-off-by: Oren Leiman <[email protected]>
Very crude request parsing, but it works well enough for existing tests. Signed-off-by: Oren Leiman <[email protected]>
This is only needed for GCS, so various identifiers will reflect that. Includes json response body parsing to get GCS-native error reasons. Signed-off-by: Oren Leiman <[email protected]>
- Wire the batch request limit (100) into remote.cc - Add switching logic in s3_client - Update cloud_io/remote_test Signed-off-by: Oren Leiman <[email protected]>
Bit simpler than retrofitting s3_client_test. Just flexing the batch delete code. Signed-off-by: Oren Leiman <[email protected]>
8453fb8 to
93cf120
Compare
|
/cdt |
1 similar comment
|
/cdt |
stating content-type: json might cause the batch backend to expect a generation or version specified, resulting in 404.
61a56ed to
9bc5489
Compare
|
/cdt |
9bc5489 to
aa577c1
Compare
|
/cdt |
|
/cdt |
|
superseded by #29246 |
Builds on #29143
Backports Required
Release Notes
Improvements