This is a tracking issue for implementing checksum support.
Checksums in an S3 transfer manager are a bit tricky due to requests being potentially split into concurrent ranged GET or multipart uploads for get and put object respectively.
We probably want to put together a design doc for this. Need to cover all known use cases including but not limited to:
Uploads:
Letting users control checksums for each part for uploads
Downloads
Giving users the ability to see individual part checksums?
Both
Try to have request/response types prevent users from constructing impossible to fulfill requests. Right now the input/output response types mirror the aws_sdk_s3 API (or more specifically our API tries to look like a single Get/Put object request/response but maybe they shouldn't).
This is a tracking issue for implementing checksum support.
Checksums in an S3 transfer manager are a bit tricky due to requests being potentially split into concurrent ranged
GETor multipart uploads for get and put object respectively.We probably want to put together a design doc for this. Need to cover all known use cases including but not limited to:
Uploads:
Downloads
Both
aws_sdk_s3API (or more specifically our API tries to look like a single Get/Put object request/response but maybe they shouldn't).