Upload a part of an ongoing multipart upload
Upload a single part of an ongoing multipart upload. Parts can be uploaded in parallel and then combined afterwards.
Path parameters
The key of the file to upload
Query parameters
The name of the bucket.
The name of the bucket the multipart upload belongs to
A unique identifier for a multipart upload
The ID of the ongoing multipart upload
The number of this part
The part number of the part being uploaded
The number of data shards a piece of an object gets erasure-coded into
Used to override the minimum number of shards the part should be split into.
The number of total data shards a piece of an object gets erasure-coded into
Used to override the total number of shards the part should be split into.
The offset of the part within the final object. This is required unless the upload was explicitly created to not be encrypted before erasure coding.
Response
Successfully uploaded part
Changes
Changed in 3 of the 50 revisions of this API.1349
- ▲
for the
queryrequest parameterminshards, default value10was addedrequest-parameter-default-value-added
- ▲
for the
queryrequest parametertotalshards, default value30was addedrequest-parameter-default-value-added
- ▲
added the pattern
^[0-9a-fA-F]{64}$to thequeryrequest parameteruploadidrequest-parameter-pattern-added
- ▲
for the
queryrequest parameterminshards, the type/format was changed frominteger/uint32tointeger/uint8request-parameter-type-changed
- ▲
for the
queryrequest parametertotalshards, the type/format was changed frominteger/uint32tointeger/uint8request-parameter-type-changed
- ●
for the
queryrequest parameterpartnumber, the max was set to10000.00request-parameter-max-set
- ●
for the
queryrequest parameterminshards, the min was set to1.00request-parameter-min-set
- ●
for the
queryrequest parameterpartnumber, the min was set to1.00request-parameter-min-set
- ●
for the
queryrequest parametertotalshards, the min was set to2.00request-parameter-min-set
- ○
for the
queryrequest parameterpartnumber, the type/format was generalized frominteger/uint32tointeger/request-parameter-type-generalized
- ○
for the
queryrequest parameteruploadid, the type/format was generalized from/tostring/request-parameter-type-generalized
- ▲
- ▲
removed the media type
text/plainfor the response with the status400response-media-type-removed
- ▲
removed the media type
text/plainfor the response with the status404response-media-type-removed
- ▲
removed the media type
text/plainfor the response with the status503response-media-type-removed
- ○
api tag
workeraddedapi-tag-added
- ▲
- ▲
for the
queryrequest parameterminshards, default value10was removedrequest-parameter-default-value-removed
- ▲
for the
queryrequest parametertotalshards, default value30was removedrequest-parameter-default-value-removed
- ▲
for the
queryrequest parameterminshards, the type/format was changed frominteger/uint8tointeger/uint32request-parameter-type-changed
- ▲
for the
queryrequest parameterpartnumber, the type/format was changed frominteger/tointeger/uint32request-parameter-type-changed
- ▲
for the
queryrequest parametertotalshards, the type/format was changed frominteger/uint8tointeger/uint32request-parameter-type-changed
- ○
api tag
workerremovedapi-tag-removed
- ○
removed the pattern
^[0-9a-fA-F]{64}$from thequeryrequest parameteruploadidrequest-parameter-pattern-removed
- ○
for the
queryrequest parameteruploadid, the type/format was generalized fromstring/to/request-parameter-type-generalized
- ○
added the media type
text/plainfor the response with the status400response-media-type-added
- ○
added the media type
text/plainfor the response with the status404response-media-type-added
- ○
added the media type
text/plainfor the response with the status503response-media-type-added
This revision also has 99 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲