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

["Andrew Gaul (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCLOUDS-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Gaul resolved JCLOUDS-1582.
----------------------------------
    Fix Version/s: 2.4.0
         Assignee: Timur Alperovich
       Resolution: Fixed

> 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
>            Assignee: Timur Alperovich
>            Priority: Minor
>              Labels: transient
>             Fix For: 2.4.0
>
>
> 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)