...
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 409 (Conflict) error. If your application updates objects faster than once per second, include Include the |
|---|---|---|
newname | Renames object | To Use the newname query argument to 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 Requests for the original name return a 404 Not Found and the prior search metadata is removed after an object is renamed. ( Note that : the |
preserve | Updates custom headers | PUT only saves new headers, but the |
...
| Info |
|---|
NoteThe object can be erasure-coded, which has a smaller storage footprint, if a non-erasure-coded object is updated and the update causes the object to meet the criteria described in Erasure Coding. |
UPDATE for alias objects
To update alias object, adding aliasAdding alias=yes is optional to update alias object because this method applies only to mutable objects.
If UPDATE succeeds on an alias object, the The content sent in the body of the request will be written as a new object if UPDATE succeeds on an alias object. The first line of the HTTP PUT will be updated to point to the new object, and the original UUID of the object is returned to the client.
...
Error Responses to UPDATE
If you execute Swarm responds with 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, Swarm responds with 409 Conflict.
| Info |
|---|
Rapid updatesRapid 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 |
...