You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example, I uploaded a 25MB file in chunks of 20MB, so the numberParts part of that adds up. I also used an S3 client for Go that calculates the MD5 of the concatenated MD5 bytes for each part, and that is consistent as well.
When completing a similar multipart upload against Riak CS, the ETag attribute looks different (it actually looks like the UploadId):
Unfortunately, clients who use this ETag to confirm that all of the parts in a multipart upload request completed successfully are not able to do so against Riak CS.
The text was updated successfully, but these errors were encountered:
When completing a multipart upload against Amazon S3, the XML payload contains a specialized
ETag
:According to a response from an Amazon employee on their support forums, this
ETag
is:In this example, I uploaded a
25MB
file in chunks of20MB
, so thenumberParts
part of that adds up. I also used an S3 client for Go that calculates the MD5 of the concatenated MD5 bytes for each part, and that is consistent as well.When completing a similar multipart upload against Riak CS, the
ETag
attribute looks different (it actually looks like theUploadId
):Response from multipart upload initialization to show that the
ETag
is theUploadId
:Unfortunately, clients who use this
ETag
to confirm that all of the parts in a multipart upload request completed successfully are not able to do so against Riak CS.The text was updated successfully, but these errors were encountered: