registry team mailing list archive

[gholt <665164@xxxxxxxxxxxxxxxxxx>]

No, that's not unworkable. The argument against is that you'd be
deleting an object the user never issued a delete for (but did issue a
delete on the container, though they didn't know the object was there).
Currently, you can only delete empty containers, so you have to
explicitly delete objects first. This is so a user can't just delete a
container with millions of objects causing us to have to have background
jobs that clean that up (and don't allow conflicts with a new container
with the same name, etc.)

Like Mike said, the one in a... gazillion? chance of container
resurrection is probably fine. But for some reason somebody was dead set
against resurrections at some point. My memory is horrible, so it was
probably me. :) I'm really fine with very rare resurrections. Kinda like
a lost+found. Heh.

I'd rather err on resurrecting something the user thought they'd deleted
implicitly than err on deleting something they never issued an explicit
delete for.

-- 
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack Object Storage (swift).
https://bugs.launchpad.net/bugs/665164

Title:
  Container DELETEs should only need a node majority to succeed