[
https://issues.apache.org/jira/browse/JCLOUDS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109836#comment-14109836
]
Niraj Tolia commented on JCLOUDS-684:
-------------------------------------
Given the relatively high-overhead of this operation and the number of RTTs
required to clear a reasonable-sized container, would it make sense to leave
the API as-is and attempt to just delete the container first and only
list/delete objects if the initial DELETE fails?
Also, I believe there are at least a couple of vendors out there, including
Cleversafe, that support non-empty container deletes with an S3 API.
> Add option to delete containers without deleting objects inside it
> ------------------------------------------------------------------
>
> Key: JCLOUDS-684
> URL: https://issues.apache.org/jira/browse/JCLOUDS-684
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-blobstore
> Affects Versions: 1.8.0
> Reporter: Shri Javadekar
>
> Some blobstores such as Microsoft Azure[1] have the ability to delete
> containers even when they are not empty. These object stores simply return
> after marking the containers for deletion and asynchronously delete the blobs
> and container in which the blobs exist.
> jclouds should have an option by which calling deleteContainer() should
> simply issue the delete request to the blobstore. It should not internally
> try and delete all the blobs in the container.
> [1] http://msdn.microsoft.com/en-us/library/azure/dd179408.aspx
--
This message was sent by Atlassian JIRA
(v6.2#6252)
