| Crates.io | aws-multipart-upload |
| lib.rs | aws-multipart-upload |
| version | 0.1.0-alpha.1 |
| created_at | 2025-03-17 08:55:39.287728+00 |
| updated_at | 2025-03-17 08:55:39.287728+00 |
| description | AWS S3 multipart upload sinks |
| homepage | |
| repository | https://github.com/quasi-coherent/aws-multipart-upload |
| max_upload_size | |
| id | 1595215 |
| size | 131,072 |
First version of a crate with futures::Sinks for doing an AWS S3 multipart upload using the official
SDK.
Current:
Upload: For the finite case, send items to Upload until they are exhausted or the (optional)
target upload size is reached. Flushing or closing the sink completes the upload. Attempting to
send more items after an upload is an error. For this reason, it's probably not a good idea to
configure it with a target upload size, unless it's really a "maximum upload size" and a very safe
upper bound on the total bytes.Development:
UploadForever: For the infinite case, UploadForever uses an iterator of S3 addresses to
continuously build and upload parts, complete uploads when the target upload size is achieved, and
then start new uploads from the next address iterator. If next returns None, this is an
error.