-
Notifications
You must be signed in to change notification settings - Fork 534
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
fix(services/s3): Batch max operations from config #2354
fix(services/s3): Batch max operations from config #2354
Conversation
…into batch_max_operations-from-config
…/manulpatel/incubator-opendal into batch_max_operations-from-config
@@ -314,6 +314,8 @@ pub struct S3Builder { | |||
/// the part size of s3 multipart upload, which should be 5 MiB to 5 GiB. | |||
/// There is no minimum size limit on the last part of your multipart upload | |||
write_min_size: Option<usize>, | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a new function for batch_max_operations
so that users can assign it.
…/manulpatel/incubator-opendal into batch_max_operations-from-config
The next step is load |
@@ -19,6 +19,7 @@ use std::collections::HashMap; | |||
use std::fmt::Debug; | |||
use std::fmt::Formatter; | |||
use std::fmt::Write; | |||
use std::string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not seeing why we need to use std::string
here.
Related issue: #2228
This PR allows to read
batch_max_operations
from config and takes default value of 1000 if not specified explicity.