Multi-delete does not remove SLO segments

[Andrew Gaul]

While this is consistent with the default behavior of DELETE which requires the manifest parameter to remove segments, I cannot efficiently emulate deleting SLOs with bulk-delete. For regular deletes, I can issue a HEAD to determine whether an object is a regular object or SLO, then issue a DELETE with the correct flags (although I would prefer DELETE to just do the right thing). For multi-delete, I would need to issue a HEAD and possibly DELETE per object, defeating the purpose of multi-delete. This makes it difficult to use a cross-cloud abstraction like jclouds to interact with both S3 and Swift. A recent user data point:

https://mail-archives.apache.org/mod_mbox/jclouds-user/201705.mbox/%3C405978882.2392930.1495023047044%40mail.yahoo.com%3E

Please make multi-delete (and delete) remove SLO segments.

[Timur Alperovich (timur-alperovich)]

We could make the bulk delete middleware aware of the multipart-manifest=delete parameter, which would be propagated on delete requests. In conjunction with https://review.openstack.org/#/c/463849/, we could delete all objects with the same single request.

[Archana (archupsg03)]

Is this same for DLO upload also ?

If not, how will the request look like for DLO bulk-delete ?

[Timur Alperovich (timur-alperovich)]

DLO support in Swift does not have a mechanism to remove all of the segments as part of removing the manifest. Given the eventual consistency issues with LIST, I suspect it was never added as an option as there is no guarantee that all of the segments will be removed.

However, I think that would be a useful option to add (with the caveats of eventual consistency).