jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCLOUDS-1450) Multi-part upload against the filesystem provider should return ETag similar to S3
Date Wed, 24 Oct 2018 20:47:00 GMT

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

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

> 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: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 2.1.1
>            Reporter: Timur Alperovich
>            Assignee: Timur Alperovich
>            Priority: Minor
>              Labels: filesystem
>             Fix For: 2.2.0
>
>
> 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)

Mime
View raw message