[
https://issues.apache.org/jira/browse/JCLOUDS-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-1450:
---------------------------------
Issue Type: Improvement (was: Bug)
> 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
> Priority: Minor
> 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)
