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
..
functional	Merge "py3: Finish porting func tests"	2019-08-22 08:13:41 +00:00
probe	py3: (mostly) port probe tests	2019-09-04 10:17:45 -07:00
s3api	Have a separate s3api functional test suite	2019-05-13 14:03:03 -07:00
unit	Sharding: Use the metadata timestamp as last_modified	2019-09-23 13:43:09 -07:00
__init__.py	Refactoring, test infrastructure changes and cleanup	2018-05-15 18:18:25 +01:00
sample.conf	Merge "Note s3api compatability requirements in sample.conf"	2019-06-05 04:11:55 +00:00