[
https://issues.apache.org/jira/browse/JCLOUDS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126123#comment-14126123
]
Andrew Gaul commented on JCLOUDS-651:
-------------------------------------
Presently the portable implementation lacks support for {CopyOptions}. Reading
through the Azure, S3, and Swift implementations, Azure and S3 support similar
options, allowing conditional copies based on modified date and ETag, and
either copying or replacement of metadata. Swift does not appear to support
any of these operations, although it does support *additional* metadata headers
to overwrite the copied headers. Given that none of these options intersect
between all providers, I propose that we only expose the minimum functionality,
copying objects while preserving metadata, in the initial implementation. We
will provide an empty {CopyOptions} for future expansion, and possibly throwing
{UnsupportedOperationException} when a providers does not support a given
option.
> server-side copy in portable abstraction
> ----------------------------------------
>
> Key: JCLOUDS-651
> URL: https://issues.apache.org/jira/browse/JCLOUDS-651
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-blobstore
> Affects Versions: 1.8.0
> Reporter: Andrew Gaul
> Assignee: Andrew Gaul
>
> jclouds should expose the provider server-side copy functionality in the
> portable abstraction. When a provider does not support this, jclouds should
> fall back to client-side copying. Amazon S3 and likely others provide this
> feature:
> http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectCOPY.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
