[
https://issues.apache.org/jira/browse/JCLOUDS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749668#comment-13749668
]
ASF subversion and git services commented on JCLOUDS-251:
---------------------------------------------------------
Commit d60d2681d1d7d7a38bbb65d5408672ee71b15727 in branch refs/heads/master
from [~francis]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=d60d268 ]
JCLOUDS-251: Swift: Delete chunks when deleting a multipart blob
Also:
- Make SwiftBlobIntegrationLiveTest.testMultipartChunkedFileStream more
realistic by uploading a file large enough to be split into parts.
- JavaDoc fixes for SwiftBlobStore: don't reference nonexistent methods.
> Swift: Delete chunks when deleting a multipart blob
> ---------------------------------------------------
>
> Key: JCLOUDS-251
> URL: https://issues.apache.org/jira/browse/JCLOUDS-251
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-blobstore
> Affects Versions: 1.6.0
> Reporter: Francis Devereux
> Priority: Minor
>
> jclouds automatically creates a blob for each chunk when it does a multipart
> upload.
> When the multipart blob is deleted with BlobStore.removeBlob() the chunks are
> left behind. It would be nice if jclouds automatically deleted them.
> Test case here:
> https://github.com/brightinteractive/jclouds-prototype/blob/1cfa515b15658b3b7f74b2714dbf5b47fb4e14f2/src/test/java/com/brightinteractive/jclouds/PutGetDeleteMultiPartTest.java
> (it fails at the last assert, assertEquals(0,
> blobStore.countBlobs(container))).
> IMHO the automatic deletion doesn't need to be optional which means no API
> changes are needed - if jclouds automatically creates chunks why shouldn't it
> always automatically delete them?
> JCLOUDS-250 probably needs to be addressed before this issue otherwise
> jclouds might automatically delete other blobs whose names start with the
> multipart blob's name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
