From d6b712dfa2a49b9bf8eef25d228056f980f1865b Mon Sep 17 00:00:00 2001 From: Tim Burke Date: Mon, 2 Dec 2024 14:38:37 -0800 Subject: [PATCH] api-ref: Clarify eventual-consistency of DELETEs. Change-Id: Ib868258b224d97ebd1c14d5b5b98bb0718caaea9 --- api-ref/source/storage-object-services.inc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/api-ref/source/storage-object-services.inc b/api-ref/source/storage-object-services.inc index 9593a96664..2519b5973d 100644 --- a/api-ref/source/storage-object-services.inc +++ b/api-ref/source/storage-object-services.inc @@ -453,13 +453,13 @@ Delete object Permanently deletes an object from the object store. -Object deletion occurs immediately at request time. Any subsequent -GET, HEAD, POST, or DELETE operations will return a ``404 Not Found`` -error code. +Object deletion occurs as soon as possible. Subsequent GET, HEAD, POST, +or DELETE operations should return a ``404 Not Found`` error code, but +may return stale data due to eventual consistency. -For static large object manifests, you can add the ``?multipart- -manifest=delete`` query parameter. This operation deletes the -segment objects and, if all deletions succeed, this operation +For static large object manifests, you can add the +``?multipart-manifest=delete`` query parameter. This operation deletes +the segment objects and, if all deletions succeed, this operation deletes the manifest object. A DELETE request made to a symlink path will delete the symlink