swift/test/unit
Matthew Oliver 370ac4cd70 Sharding: Use the metadata timestamp as last_modified
This is a follow up patch from the cleaning up cleave context's patch
(patch 681970). Instead of tracking a last_modified timestamp, and storing
it in the context metadata, use the timestamp we use when storing any
metadata.

Reducing duplication is nice, but there's a more significant reason to
do this: affected container DBs can start getting cleaned up as soon as
they're running the new code rather than needing to wait for an
additional reclaim_age.

Change-Id: I2cdbe11f06ffb5574e573c4a60ba4e5d41a00c50
2019-09-23 13:43:09 -07:00
..
account py3: fix non-ascii metadata handling in account-server 2019-07-25 14:16:56 -07:00
cli Sharding: Use the metadata timestamp as last_modified 2019-09-23 13:43:09 -07:00
common Merge "Rename symlink method" 2019-08-20 13:12:22 +00:00
container Sharding: Use the metadata timestamp as last_modified 2019-09-23 13:43:09 -07:00
obj ec: log durability of frags that fail to reconstruct 2019-08-20 22:23:00 -07:00
proxy Merge "py3: fix up listings on sharded containers" 2019-08-28 07:37:16 +00:00
test_locale py3: port the test of locale 2019-06-19 09:54:14 -07:00
__init__.py Fix test_parse_get_node_args 2019-07-19 01:32:25 +02:00
helpers.py Increase node_timeout for real sever unittests 2019-08-05 15:40:58 -05:00