Open Stack

Hi,

I have a question regarding the way object overwrites work in the
absence of versioning. I couldn't find this info in the documentation.

Consider the case when I have an object O already present in the Swift
cluster. There are N replicas of this object. When a new PUT request
that overwrites object O is returned, Swift guarantees that the new
object, say O' got written successfully to N/2 + 1 object servers. But
there could be some replicas that still have the older object O.

Does Swift have a way of invalidating the older object O on all object servers?

If there is a GET request for object O, immediately after the
overwrite, does Swift guarantee that the older object O cannot be
returned?

Thanks in advance.
-Shri