Implement correctly ETags for multipart uploads #3

Closed
opened 2020-07-13 14:54:54 +00:00 by lx · 1 comment
Owner

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).

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).
lx added the
Low priority
label 2020-07-13 14:55:39 +00:00
lx added the
S3 Compatibility
label 2021-02-18 17:19:02 +00:00
Author
Owner

Done in dev-0.2

Done in `dev-0.2`
lx closed this issue 2021-03-10 16:47:58 +00:00
lx added this to the 0.2 milestone 2021-03-10 16:48:02 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#3
No description provided.