Versions Compared

Key

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

...

The UPDATE request is formatted as a simple an HTTP request using the PUT method.

...

replicate

Protects rapid updates

Important: 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 an HTTP 409 (Conflict) error. Include the replicate=immediate query argument to verify more than one node returns the latest version in a subsequent read if an application updates objects faster than once per second.

newname

Renames object

Use the newname query argument to rename a named object within the same bucket, which provides a new name with the update request (PUT, COPY, APPEND). Requests for the original name return a an HTTP 404 Not Found and the prior search metadata is removed after an object is renamed. Note: the newname argument also allows renaming domains and buckets.

preserve

Updates custom headers

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

...

UPDATE is a request to the storage cluster to modify a specific named object or alias object with new content. The UPDATE request is formatted as a simple an HTTP request using the PUT method:

...

The UPDATE request is formatted as a simple an HTTP request using the PUT method. The normal response to a PUT request, similar to a POST, is a an HTTP 201 Created response.

Code Block
languagebash
PUT /06eec5e2c3f1aadcb41ef7fd52adc049 HTTP/1.1
  Host: cluster.example.com
  User-Agent: Swarm Client/0.1 
  Content-Length: 43402 
  Expect: 100-continue
  Content-Type: image/jpeg
  Content-Language: en/us, x-pig-latin
  Content-Version: 42
  Last-Modified: Wed, 1 Sept 2010 15:59:02 GMT
  Created-Date: Wed, 1 Sept 2010 15:59:02 GMT
  CRLF
  [ content ]

PUT returns a an HTTP 404 Not Found error if the object name or UUID you specify in the command does not exist.

...

Normal Responses to UPDATE

For See SCSP Headers for a list of response headers, see SCSP Headers.

Error Responses to UPDATE

Swarm responds with an HTTP 409 Conflict if the UPDATE method is executed on an object in a domain but the domain does not exist or is not in the content cache on the node that receives the request.

Info

Rapid updates

Rapid updates of an object can trigger a an HTTP 409 Conflict error, 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). Those unlisted versions are accessible directly by the versionid. Using a 1-second delay should avoid this.

...