[
https://issues.apache.org/jira/browse/JCLOUDS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241346#comment-16241346
]
ASF subversion and git services commented on JCLOUDS-1111:
----------------------------------------------------------
Commit b2ced53e165ecbea4188e2d2673a7ddb2f5a793d in jclouds's branch
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=b2ced53 ]
JCLOUDS-1111: Overwrite objects via remove and put
This partially reverts commit
e446b5b8b433327d8a11c0364abb051cff833431. AT&T Synaptic returns a
bogus error on with x-emc-force-overwrite:
HTTP 400, code=1012, message=There was a mismatch between the object
size and the specified extent size.
> AtmosClient.createFile should allow overwriting objects
> -------------------------------------------------------
>
> Key: JCLOUDS-1111
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1111
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-blobstore
> Affects Versions: 1.9.2
> Reporter: Andrew Gaul
> Assignee: Andrew Gaul
> Labels: atmos
> Fix For: 2.1.0
>
>
> All other blobstore providers support overwrite semantics yet Atmos raises a
> 1006 error. Thus I believe we should send {{x-emc-force-overwrite}} for all
> {{AtmosClient.createFile}} calls which will improve the overwrite performance
> of {{AtmosBlobStore.putBlob}}. We could optionally allow the existing
> semantics by adding another field to {{PutOptions}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
