Implement correctly ETags for multipart uploads #3
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
See this site for info on how they are calculated : https://teppen.io/2018/06/23/aws_s3_etags/
Not sure if anyone ever checks ETags in this way, the AWS docs say that in case of a multipart upload the ETag should be considered as an opaque value so it is probably not necessary to it like described in the link. It would also be quite hard as the MD5 sums of individual parts has to be added to the metadata database (currently it only stores sha256 sums of blocks, which are themselves chunks of the uploaded parts).
Done in
dev-0.2
jpds referenced this issue2023-08-04 08:19:30 +00:00