> + switch (md.getType()) {
> + case BLOB:
> + blobDelFuture = executorService.submit(new Callable<Void>() {
> + @Override
> + public Void call() {
> + blobStore.removeBlob(containerName, fullPath);
> + return null;
> + }
> + });
> + break;
> + case FOLDER:
> + if (options.isRecursive()) {
> + blobDelFuture = executorService.submit(new Callable<Void>() {
> + @Override
> + public Void call() {
> + blobStore.deleteDirectory(containerName, fullPath);
Previously ```clearContainer``` issued a batch of delete blob operations within
a subtree before removing the parent but now it can issue delete blob
operations concurrently with delete parent. I believe the new logic will
generate operation failures. This is generally a hard problem to solve; can we
simplify this for now by making the recursive call blocking?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/214/files#r10912447
