You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2018/09/21 19:27:01 UTC

[jira] [Updated] (JCLOUDS-1450) Multi-part upload against the filesystem provider should return ETag similar to S3

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

Andrew Gaul updated JCLOUDS-1450:
---------------------------------
    Labels: filesystem  (was: )

> Multi-part upload against the filesystem provider should return ETag similar to S3
> ----------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-1450
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1450
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 2.1.1
>            Reporter: Timur Alperovich
>            Priority: Major
>              Labels: filesystem
>
> When performing a multi-part upload in S3, the resulting ETag is not a content hash, but rather a hash of the content hashes of the parts, followed by "-<number of parts>". It would be great for the jclouds filesystem provider to have the same behavior if it's trying to be an emulation for S3 (or Swift, which has a similar behavior for its Static Large Objects).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)