Add doc example for multipart upload to MicrosoftAzure::create_multipart#802
Open
alamb wants to merge 1 commit into
Open
Add doc example for multipart upload to MicrosoftAzure::create_multipart#802alamb wants to merge 1 commit into
MicrosoftAzure::create_multipart#802alamb wants to merge 1 commit into
Conversation
Add a runnable (`no_run`) example on the `MultipartStore` impl for `MicrosoftAzure` showing the full low-level flow: `create_multipart`, `put_part` for each part, and `complete_multipart` to finalize. Also link to the example from `MultipartStore::create_multipart` so it is discoverable from the trait definition. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
alamb
commented
Jul 10, 2026
| /// Azure stores each part as a block, so a single blob may contain at most | ||
| /// 50,000 parts, each up to 4,000 MiB. Parts may be uploaded concurrently and | ||
| /// in any order, provided each is given the correct `part_idx`. See | ||
| /// [Azure block blob limits] for the full set of size and count constraints. |
Contributor
There was a problem hiding this comment.
from https://learn.microsoft.com/en-us/rest/api/storageservices/put-block
which is already linked in the comment, 👍
kevinjqliu
approved these changes
Jul 18, 2026
kevinjqliu
left a comment
Contributor
There was a problem hiding this comment.
LGTM i tested this against my azure storage account, works like a charm
| /// Azure stores each part as a block, so a single blob may contain at most | ||
| /// 50,000 parts, each up to 4,000 MiB. Parts may be uploaded concurrently and | ||
| /// in any order, provided each is given the correct `part_idx`. See | ||
| /// [Azure block blob limits] for the full set of size and count constraints. |
Contributor
There was a problem hiding this comment.
from https://learn.microsoft.com/en-us/rest/api/storageservices/put-block
which is already linked in the comment, 👍
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
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.

Rationale for this change
The low-level
MultipartStoreAPI had no worked example showing the fullcreate_multipart→put_part→complete_multipartflow. This adds one for Azure, mirroring the S3 example in #801.What changes are included in this PR?
no_run) doc example onMicrosoftAzure::create_multipartshowing the full low-level flow.Are there any user-facing changes?
Documentation only. No API changes.