[FEATURE] Batch Bucket Management: Sequential and Parallel Operations #1509
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 5 commits
September 7, 2025 14:13
…support for parallelism
…ture_bulk_bucket_operations
ShubhamKaudewar
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Community,
This PR aims to introduce bulk operations for bucket-related tasks. Currently, the MinIO Python SDK supports
make_bucketandremove_bucketfunctionalities, which allow users to create a single bucket with a specified region and object_lock. This PR proposes extending support to include the following multi-operation functionalities:make_bucketsmake_buckets_parallelremove_bucketsremove_buckets_parallelWhy is this needed?
Users no longer need to write wrapper functions using iterators or loops to create or remove multiple buckets. Parallel support enables bucket creation in isolated threads, improving efficiency and reducing the risk of a single point of failure that could block subsequent bucket creations.
Conclusion
Feel free to suggest changes or share feedback. Let me know if this is unnecessary at this time or if it poses any risks or requires additional sanity checks.