Complete Multipart Upload

Description

This operation will complete the block upload task before the object assembly.

After starting a block upload task, the user will use the Upload Parts interface to upload all blocks. After successfully uploading all related blocks, the user needs to call this interface to complete the block upload. After receiving the completion request, KS3 will assemble all the blocks according to the block sequence number to create a new object. In the user's task completion request, the user needs to provide a block list. Because KS3 will connect all blocks according to the list, the user is required to ensure that all blocks have been uploaded. For each block in the block list, the user needs to add the block number and the ETag header of the object when uploading the block, and KS3 will reply to complete the response after the block is uploaded.

Please note that if the Complete Multipart Upload request fails, the user application should be able to retry the operation.

Request

Syntax

POST /{ObjectKey}?uploadId={UploadId} HTTP/1.1
Host: {BucketName}.{endpoint}
Date: {Date}
Content-Length: {Size}
Authorization: {SignatureValue}

<CompleteMultipartUpload>
<Part>
<PartNumber>{PartNumber}</PartNumber>
<ETag>{ETag}</ETag>
</Part>
...
</CompleteMultipartUpload>

Attention：

• Correspondence between Endpoint and Region
• SignatureValue Algorithm

Request Parameters

The request does not use the request parameter.

Request Headers

This request uses only the common request headers. For more information, please click Public Request Headers

Request Elements

Response

Response Headers

This interface uses common response headers. For more information, please click Public Response Headers

Response Elements

Special Errors

Examples

Sample Request

POST /my-viedo.rm ?uploadId=1aa9cfad5e2e405c8f27965feb8b60cc HTTP/1.1
Host: ks3-example.ks3-cn-beijing.ksyuncs.com
Date: Mon, 1 Nov 2010 20:34:56 GMT
Content-Length: 391
Authorization: authorization string

<CompleteMultipartUpload>
    <Part>
        <PartNumber>1</PartNumber>
        <ETag>"a54357aff0632cce46d942af68356b38"</ETag>
    </Part>
    <Part>
        <PartNumber>2</PartNumber>
        <ETag>"0c78aef83f66abc1fa1e8477f296d394"</ETag>
    </Part>
    <Part>
        <PartNumber>3</PartNumber>
        <ETag>"acbd18db4cc2f85cedef654fccc4a4d8"</ETag>
    </Part>
</CompleteMultipartUpload>

Sample Response

HTTP/1.1 200 OK
Date: Mon, 1 Nov 2010 20:34:56 GMT
Connection: close
Server: Tengine

<?xml version="1.0" encoding="UTF-8"?>
<CompleteMultipartUploadResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <Location>http://ks3-example.ks3-cn-beijing.ksyuncs.com/my-video.rm</Location>
    <Bucket>ks3-example</Bucket>
    <Key>my-video.rm</Key>
    <ETag>"3858f62230ac3c915f300c664312c11f"</ETag>
</CompleteMultipartUploadResult>

Interface Detail Analysis

• Except for the last block, each block shall be at least 5MB. When the total size of the file is within 5M, each block can be at least 100k except the last block.
• The list of parts submitted by users must be in ascending order.
• When the operation is completed, the corresponding UploadId will be invalid
• The same Object can have different upload IDS at the same time. When an Upload ID is completed, other upload IDs of the object are not affected.
• Each part in the submitted part list must exist. Otherwise, InvalidPartOrder will be reported