Methods Affected by Erasure Coding

Following is how the SCSP methods are affected by erasure-coded objects:

Method	Description

Method	Description
POST	A new object written to the storage cluster is erasure-coded if it meets the EC criteria.
PUT	As with POST, if a non-erasure-coded object is PUT and the data causes the object to meet the EC criteria, the object can be erasure-coded.
APPEND	As with PUT, if data appended to a non-EC object causes the object to meet the EC criteria, the object can be erasure-coded. APPENDs are optimized to POST a new set of EC segments with the appended data and PUT the manifest for a previously erasure-coded object, instead of rewriting the whole object to include the appended data as with replicated objects. Data appended to an object not previously erasure-coded can cause the object to become erasure-coded if the additional appended data pushes the object size over the configured `ECMinStreamSize` threshold. Attempting to use the argument `erasurecoded` without `encoding` or when the cluster is not configured for EC results in an HTTP 400 Bad Request error. On an APPEND for an existing EC object, the new segments are encoded with the parameters of the first existing erasure set.
COPY	Instead of rewriting the entire object to PUT the metadata, COPY for erasure-coded objects PUTs the metadata on the manifest only without rewriting any content data.
HEAD	Returns the Manifest: ec header for an erasure-coded object.
GET	The cluster automatically retrieves all segments, so a GET does not operate differently for an erasure-coded object.
DELETE	Swarm deletes both the manifests and the segments for the object.