[
https://issues.apache.org/jira/browse/JCLOUDS-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timur Alperovich updated JCLOUDS-1582:
--------------------------------------
Description: The local transient blobstore returns a correctly computed S3
MPU ETag when completing the upload, but a subsequent GET/HEAD request returns
the MD5 of the whole object instead (not matching the ETag in the CompleteMPU
response). Ideally, jclouds should store the MPU ETag in the extended
attributes along with the object and use its value for GET/HEAD requests.
(was: The local filesystem blobstore returns a correctly computed S3 MPU ETag
when completing the upload, but a subsequent GET/HEAD request returns the MD5
of the whole object instead (not matching the ETag in the CompleteMPU
response). Ideally, jclouds should store the MPU ETag in the extended
attributes along with the object and use its value for GET/HEAD requests.)
> ETag of the object uploaded via multipart upload does not match the
> CompleteMPU response from the transient blobstore
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-1582
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1582
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 2.3.0
> Reporter: Timur Alperovich
> Priority: Minor
> Labels: filesystem
>
> The local transient blobstore returns a correctly computed S3 MPU ETag when
> completing the upload, but a subsequent GET/HEAD request returns the MD5 of
> the whole object instead (not matching the ETag in the CompleteMPU response).
> Ideally, jclouds should store the MPU ETag in the extended attributes along
> with the object and use its value for GET/HEAD requests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
