[Bug 1069849] Re: Containers show expired objects

[clayg]

nope, nope, nope - this is expected behavior.

Clients must reconcile with "objects in the listing may 404" i.e. object
listing is out of date - this is a basic tenant of the systems choice to
favor availability over consistency.

We can reduce the inaccuracies where possible, but in this case no
obvious improvement to the expierer was purposed, I think theres some
other bugs open that could acctually be implemented, e.g.

https://bugs.launchpad.net/bugs/1076202

There was a comment no-one seemed to respond to about 410 or special
messaging - I'm guessing that was about the object response for a
expired object vs. a deleted one (and has nothing to do with the
container listings).  I think that's a bad idea - but off topic for this
bug, so I'm going to pretend I didn't see it.

** Changed in: swift
       Status: Confirmed => Invalid

** Changed in: swift (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to swift in Ubuntu.
https://bugs.launchpad.net/bugs/1069849

Title:
  Containers show expired objects

To manage notifications about this bug go to:
https://bugs.launchpad.net/swift/+bug/1069849/+subscriptions