[jira] [Commented] (JCLOUDS-1582) ETag of the object uploaded via multipart upload does not match the CompleteMPU response from the transient blobstore

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393761#comment-17393761 ] 

ASF subversion and git services commented on JCLOUDS-1582:
----------------------------------------------------------

Commit a1df0bb1f5f094774c81595fe8145d6f094a9ed6 in jclouds's branch refs/heads/master from Timur Alperovich
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=a1df0bb ]

Store the MPU ETag for the transient blobstore

JCLOUDS-1582: fixes a bug in the transient blobstore where after
uploading a multipart upload, GET/HEAD returns the hash of the content,
rather than the MPU ETag.


> 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: transient
>
> 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 and return it on GET/HEAD requests.
> This behavior also manifests when using the filesystem blobstore if the extended attributes are not supported. In that case, there is nothing jclouds can do.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)