Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

replicateProtects rapid updatesImportant: Objects can be updated at a maximum frequency of once per second. Updating more frequently can cause unpredictable results with the stored object version and can trigger a 409 (Conflict) error. If your application updates objects faster than once per second, include the replicate=immediate query argument to ensure that more than one node can return the latest version in a subsequent read.
newnameRenames objectTo rename a named object within the same bucket, use the newname query argument, which provides a new name with the update request (PUT, COPY, APPEND). After you rename an object, requests for the original name return a 404 Not Found and the prior search metadata is removed. (Note that the newname argument also lets you rename allows renaming domains and buckets.)
preserveUpdates custom headers

PUT only saves new headers, but the preserve argument lets you keep allows keeping the existing headers as well as save any new ones. (v9.5)

...

Info
titleRapid updates

Rapid updates of an object can trigger a 409 Conflict error, that a "Later version already exists."

Rapid updates or overwrites to an object in a versioned bucket can cause temporary listing inconsistency, even when replication=immediate is used (default with Gateway). You can still access those unlisted versions directly by their versionid. Using a 1-second delay should avoid this.

...