| 2016-09-23 13:12:34 |
Alistair Coles |
description |
object versioning has never versioned DLO manifests (for reasons unknown to me).
With https://review.openstack.org/#/c/214922/ a new history mode of versioning was introduced that writes delete markers to the versions container when an object is deleted. These delete markers are created when a DLO manifest is deleted, but there are no versions of the DLO manifest, so the delete marker is pointless. Since none of this DLO treatment is documented, the generation of a delete marker is also confusing.
Possible actions to address this issue:
1) The introduction of history mode might have been an opportunity to have DLO manifests be versioned. Is it too late?
or
2) document the anomalous treatment of DLOs in versioned writes doc
and
3) do not create delete marker for a DLO manifest (hard because we don't know its a manifest when deleting) |
object versioning has never versioned DLO manifests (for reasons unknown to me).
With https://review.openstack.org/#/c/214922/ a new history mode of versioning was introduced that writes delete markers to the versions container when an object is deleted. These delete markers are created when a DLO manifest is deleted, but there are no versions of the DLO manifest, so the delete marker is pointless. Since none of this DLO treatment is documented, the generation of a delete marker is also confusing.
Possible actions to address this issue:
1) The introduction of history mode might have been an opportunity to have DLO manifests be versioned. Is it too late?
or
2) document the anomalous treatment of DLOs in versioned writes doc
and
3) do not create delete marker for a DLO manifest |
|
