New Object Versioning mode

Code Issues Proposed changes

This patch adds a new object versioning mode. This new mode provides
a new set of APIs for users to interact with older versions of an
object. It also changes the naming scheme of older versions and adds
a version-id to each object.
This new mode is not backwards compatible or interchangeable with the
other two modes (i.e., stack and history), especially due to the changes
in the namimg scheme of older versions. This new mode will also serve
as a foundation for adding S3 versioning compatibility in the s3api
middleware.
Note that this does not (yet) support using a versioned container as
a source in container-sync. Container sync should be enhanced to sync
previous versions of objects.
Change-Id: Ic7d39ba425ca324eeb4543a2ce8d03428e2225a1
Co-Authored-By: Clay Gerrard <clay.gerrard@gmail.com>
Co-Authored-By: Tim Burke <tim.burke@gmail.com>
Co-Authored-By: Thiago da Silva <thiagodasilva@gmail.com>

This commit is contained in:

Clay Gerrard

2019年09月13日 12:25:24 -05:00

committed by Tim Burke

parent 26ff2eb1cb

commit 2759d5d51c

33 changed files with 8307 additions and 163 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2
etc/proxy-server.conf-sample

View File

@@ -1072,6 +1072,8 @@ use = egg:swift#versioned_writes

# in the container configuration file, which will be eventually

# deprecated. See documentation for more details.

# allow_versioned_writes = false

# Enables Swift object-versioning API

# allow_object_versioning = false

# Note: Put after auth and before dlo and slo middlewares.

# If you don't put it in the pipeline, it will be inserted for you.

New Object Versioning mode

2 etc/proxy-server.conf-sample Unescape Escape View File

2
etc/proxy-server.conf-sample

View File