Performing a Multipart Upload
If you have any questions during development, post them on the Issues page of GitHub. For details about parameters and usage of each API, see the API Reference.
To upload a large file, multipart upload is recommended. Multipart upload is applicable to many scenarios, including:
- Files to be uploaded are larger than 100 MB.
- The network condition is poor. Connection to the OBS server is constantly down.
- Sizes of files to be uploaded are uncertain.
Multipart upload consists of three phases:
- Initialize a multipart upload (ObsClient.initiateMultipartUpload).
- Upload parts one by one or concurrently (ObsClient.uploadPart).
- Combine parts (ObsClient.completeMultipartUpload) or abort the multipart upload (ObsClient.abortMultipartUpload).
You can also call the API for resumable upload (encapsulation and enhancement of multipart upload) provided by the SDK to implement multipart upload.
Initializing a Multipart Upload
Before upload, you need to notify OBS of initializing a multipart upload. This operation will return an upload ID (globally unique identifier) created by the OBS server to identify the multipart upload. You can use this upload ID to initiate related operations, such as aborting a multipart upload, listing multipart uploads, and listing uploaded parts.
You can call ObsClient.initiateMultipartUpload to initialize a multipart upload.
// Create an instance of ObsClient.
var obsClient = new ObsClient({
access_key_id: '*** Provide your Access Key ***',
secret_access_key: '*** Provide your Secret Key ***',
server : 'https://your-endpoint'
});
obsClient.initiateMultipartUpload({
Bucket : 'bucketname',
Key : 'objectname',
ContentType : 'text/plain',
Metadata : {'property' : 'property-value'}
}, function (err, result) {
if(err){
console.error('Error-->' + err);
}else{
console.log('Status-->' + result.CommonMsg.Status);
if(result.CommonMsg.Status < 300 && result.InterfaceResult){
console.log('UploadId-->' + result.InterfaceResult.UploadId);
}
}
});
- When initializing a multipart upload, you can use the ContentType and Metadata parameters to respectively set the MIME type and customize the metadata of an object, besides the object name and owning bucket.
- After the API for initializing a multipart upload is called, the upload ID will be returned. This ID will be used in follow-up operations.
Uploading a Part
After initializing a multipart upload, you can specify the object name and upload ID to upload a part. Each part has a part number (ranging from 1 to 10000). For parts with the same upload ID, their part numbers are unique and identify their comparative locations in the object. If you use the same part number to upload two parts, the latter one being uploaded will overwrite the former. Except for the part last uploaded whose size ranges from 0 to 5 GB, sizes of the other parts range from 100 KB to 5 GB. Parts are uploaded in random order and can be uploaded through different processes or machines. OBS will combine them into the object based on their part numbers.
You can call ObsClient.uploadPart to upload parts.
// Create an instance of ObsClient.
var obsClient = new ObsClient({
access_key_id: '*** Provide your Access Key ***',
secret_access_key: '*** Provide your Secret Key ***',
server : 'https://your-endpoint'
});
obsClient.uploadPart({
Bucket:'bucketname',
Key:'objectname',
// Set the part number, which ranges from 1 to 10000.
PartNumber:1,
// Set the upload ID.
UploadId:'upload id from initiateMultipartUpload',
// Specify the large file to be uploaded.
SourceFile: document.getElementById('input-file').files[0],
// Set the part size.
PartSize: 5 * 1024 * 1024,
// Set the start offset.
Offset: 0
}, function (err, result) {
if(err){
console.log('Error-->' + err);
}else{
console.log('Status-->' + result.CommonMsg.Status);
if(result.CommonMsg.Status < 300 && result.InterfaceResult){
console.log('ETag-->' + result.InterfaceResult.ETag);
}
}
});
- Use the PartNumber parameter to specify the part number, the UploadId parameter to specify the globally unique ID, the SourceFile parameter to specify the to-be-uploaded file, the PartSize parameter to set the part size, and the Offset parameter to set the start offset of the file.
- SourceFile must indicate a File or Blob object. For example, on an HTML page, use an input tag whose type is file to specify the to-be-uploaded file: <input type="file" id="input-file"/>.
- Except the part last uploaded, other parts must be larger than 100 KB. Part sizes will not be verified during upload because which one is last uploaded is not identified until parts are combined.
- OBS will return ETags (MD5 values) of the received parts to users.
- You can use the ContentMD5 parameter to set the MD5 value of the uploaded data.
- Part numbers range from 1 to 10000. If the part number you set is out of this range, OBS will return error 400 Bad Request.
- The minimum part size supported by an OBS 3.0 bucket is 100 KB, and the minimum part size supported by an OBS 2.0 bucket is 5 MB. You are advised to perform multipart upload to OBS 3.0 buckets.
Combining Parts
After all parts are uploaded, call the API for combining parts to generate the object. Before this operation, valid part numbers and ETags of all parts must be sent to OBS. After receiving this information, OBS verifies the validity of each part one by one. After all parts pass the verification, OBS combines these parts to form the final object.
You can call ObsClient.completeMultipartUpload to combine parts.
// Create an instance of ObsClient.
var obsClient = new ObsClient({
access_key_id: '*** Provide your Access Key ***',
secret_access_key: '*** Provide your Secret Key ***',
server : 'https://your-endpoint'
});
obsClient.completeMultipartUpload({
Bucket:'bucketname',
Key:'objectname',
// Set the upload ID.
UploadId:'upload id from initiateMultipartUpload',
Parts: [{'PartNumber':1,'ETag':'etag value from uploadPart'}]
}, function (err, result) {
if(err){
console.log('Error-->' + err);
}else{
console.log('Status-->' + result.CommonMsg.Status);
}
});
- Use the UploadId parameter to specify the globally unique identifier for the multipart upload and the Parts parameter to specify the list of part numbers and ETags. Content in the list is displayed in the ascending order by part number.
- Part numbers can be inconsecutive.
Aborting a Multipart Upload
After a multipart upload is aborted, you cannot use its upload ID to perform any operation and the uploaded parts will be deleted by OBS.
When an object is being uploaded in multi-part mode or an object fails to be uploaded, parts are generated in the bucket. These parts occupy your storage space. You can cancel the multi-part uploading task to delete unnecessary parts, thereby saving the storage space.
You can call ObsClient.abortMultipartUpload to abort a multipart upload.
// Create an instance of ObsClient.
var obsClient = new ObsClient({
access_key_id: '*** Provide your Access Key ***',
secret_access_key: '*** Provide your Secret Key ***',
server : 'https://your-endpoint'
});
obsClient.abortMultipartUpload({
Bucket:'bucketname',
Key:'objectname',
// Set the upload ID.
UploadId:'upload id from initiateMultipartUpload',
}, function (err, result) {
if(err){
console.log('Error-->' + err);
}else{
console.log('Status-->' + result.CommonMsg.Status);
}
});
Listing Uploaded Parts
You can call ObsClient.listParts to list successfully uploaded parts of a multipart upload.
The following table describes the parameters involved in this API.
|
Parameter |
Description |
|---|---|
|
UploadId |
Upload ID, which globally identifies a multipart upload. The value is in the returned result of ObsClient.initiateMultipartUpload. |
|
MaxParts |
Maximum number of parts that can be listed per page. |
|
PartNumberMarker |
Part number after which listing uploaded parts begins. Only parts whose part numbers are larger than this value will be listed. |
- Listing parts in simple mode
// Create an instance of ObsClient.
var obsClient = new ObsClient({
access_key_id: '*** Provide your Access Key ***',
secret_access_key: '*** Provide your Secret Key ***',
server : 'https://your-endpoint'
});
// List uploaded parts. uploadId is obtained from initiateMultipartUpload.
obsClient.listParts({
Bucket : 'bucketname',
Key: 'objectname',
UploadId : 'upload id from initiateMultipartUpload'
}, function (err, result) {
if(err){
console.log('Error-->' + err);
}else{
console.log('Status-->' + result.CommonMsg.Status);
if(result.CommonMsg.Status < 300 && result.InterfaceResult){
for(var i in result.InterfaceResult.Parts){
console.log('Part['+ i +']:');
// Part number, specified upon uploading
console.log('PartNumber-->' + result.InterfaceResult.Parts[i]['PartNumber']);
// Time when the part was last uploaded
console.log('LastModified-->' + result.InterfaceResult.Parts[i]['LastModified']);
// Part ETag
console.log('ETag-->' + result.InterfaceResult.Parts[i]['ETag']);
// Part size
console.log('Size-->' + result.InterfaceResult.Parts[i]['Size']);
}
}
}
});
- Information about a maximum of 1000 parts can be listed each time. If an upload of the specific upload ID contains more than 1000 parts and InterfaceResult.IsTruncated is true in the returned result, not all part information is returned. In such cases, you can use InterfaceResult.NextPartNumberMarker to obtain the start position for next listing.
- If you want to obtain all parts involved in a specific upload ID, you can use the paging mode for listing.
- Listing all parts
If the number of parts of a multipart upload is larger than 1000, you can use the following sample code to list all parts.
// Create an instance of ObsClient.
var obsClient = new ObsClient({
access_key_id: '*** Provide your Access Key ***',
secret_access_key: '*** Provide your Secret Key ***',
server : 'https://your-endpoint'
});
var listAll = function (partNumberMarker) {
// List uploaded parts. uploadId is obtained from initiateMultipartUpload.
obsClient.listParts({
Bucket : 'bucketname',
Key: 'objectname',
UploadId : 'upload id from initiateMultipartUpload',
PartNumberMarker : partNumberMarker
}, function (err, result) {
if(err){
console.log('Error-->' + err);
}else{
console.log('Status-->' + result.CommonMsg.Status);
if(result.CommonMsg.Status < 300 && result.InterfaceResult){
for(var i in result.InterfaceResult.Parts){
console.log('Part['+ i +']:');
// Part number, specified upon uploading
console.log('PartNumber-->' + result.InterfaceResult.Parts[i]['PartNumber']);
// Time when the part was last uploaded
console.log('LastModified-->' + result.InterfaceResult.Parts[i]['LastModified']);
// Part ETag
console.log('ETag-->' + result.InterfaceResult.Parts[i]['ETag']);
// Part size
console.log('Size-->' + result.InterfaceResult.Parts[i]['Size']);
}
if(result.InterfaceResult.IsTruncated === 'true'){
listAll(result.InterfaceResult.NextPartNumberMarker);
}
}
}
});
};
listAll();
Listing Multipart Uploads
You can call ObsClient.listMultipartUploads to list multipart uploads. The following table describes parameters involved in ObsClient.listMultipartUploads.
|
Parameter |
Description |
|---|---|
|
Prefix |
Prefix that the object names in the multipart uploads to be listed must contain |
|
Delimiter |
Character used to group object names involved in multipart uploads. If the object name contains the Delimiter parameter, the character string from the first character to the first delimiter in the object name is grouped under a single result element, CommonPrefix. (If a prefix is specified in the request, the prefix must be removed from the object name.) |
|
MaxUploads |
Maximum number of returned multipart uploads. The value ranges from 1 to 1000. If the value is not in this range, 1000 multipart uploads are returned by default. |
|
KeyMarker |
Object name to start with when listing multipart uploads |
|
UploadIdMarker |
Upload ID after which the multipart upload listing begins. It is effective only when used with KeyMarker so that multipart uploads after UploadIdMarker of KeyMarker will be listed. |
- Listing multipart uploads in simple mode
// Create an instance of ObsClient.
var obsClient = new ObsClient({
access_key_id: '*** Provide your Access Key ***',
secret_access_key: '*** Provide your Secret Key ***',
server : 'https://your-endpoint'
});
obsClient.listMultipartUploads({
Bucket : 'bucketname'
}, function (err, result) {
if(err){
console.log('Error-->' + err);
}else{
console.log('Status-->' + result.CommonMsg.Status);
if(result.CommonMsg.Status < 300 && result.InterfaceResult){
for(var i in result.InterfaceResult.Uploads){
console.log('Uploads[' + i + ']');
console.log('UploadId-->' + result.InterfaceResult.Uploads[i]['UploadId']);
console.log('Key-->' + result.InterfaceResult.Uploads[i]['Key']);
console.log('Initiated-->' + result.InterfaceResult.Uploads[i]['Initiated']);
}
}
}
});
- Information about a maximum of 1000 multipart uploads can be listed each time. If a bucket contains more than 1000 multipart uploads and InterfaceResult.IsTruncated is true in the returned result, not all uploads are listed. In such cases, you can use InterfaceResult.NextKeyMarker and InterfaceResult.NextUploadIdMarker to obtain the start position for next listing.
- If you want to obtain all multipart uploads in a bucket, you can list them in paging mode.
- Listing all multipart uploads
// Create an instance of ObsClient.
var obsClient = new ObsClient({
access_key_id: '*** Provide your Access Key ***',
secret_access_key: '*** Provide your Secret Key ***',
server : 'https://your-endpoint'
});
var listAll = function (keyMarker, uploadIdMarker) {
obsClient.listMultipartUploads({
Bucket : 'bucketname',
KeyMarker : keyMarker,
UploadIdMarker : uploadIdMarker
}, function (err, result) {
if(err){
console.log('Error-->' + err);
}else{
console.log('Status-->' + result.CommonMsg.Status);
if(result.CommonMsg.Status < 300 && result.InterfaceResult){
for(var i in result.InterfaceResult.Uploads){
console.log('Uploads[' + i + ']');
console.log('UploadId-->' + result.InterfaceResult.Uploads[i]['UploadId']);
console.log('Key-->' + result.InterfaceResult.Uploads[i]['Key']);
console.log('Initiated-->' + result.InterfaceResult.Uploads[i]['Initiated']);
}
if(result.InterfaceResult.IsTruncated === 'true'){
listAll(result.InterfaceResult.NextKeyMarker, result.InterfaceResult.NextUploadIdMarker);
}
}
}
});
}
listAll();
Last Article: Setting Object Properties
Next Article: Configuring Lifecycle Management
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.