Skip to content

Latest commit

 

History

History
54 lines (38 loc) · 5.99 KB

list_multipart_uploads.md

File metadata and controls

54 lines (38 loc) · 5.99 KB
Raw

List Multipart Uploads

Get a list of ongoing multipart upload objects. When an object has the segment upload mode enabled via the Initiate Multipart interface, the object is in the "multiply uploading" state before the Complete Multipart or Abort Multipart interface is called. This object will appear in the list returned by the interface.

Similar to the GET Bucket (List Objects) interface, the user can specify the segment upload that is being performed under a directory by passing the prefix, delimiter request parameter. The list is sorted from small to large in alphanumeric order of object names. If there are multiple segments uploaded by the same-named object, only one part of the page is truncated, and the next page-turning can be obtained by upload_id_marker parameter to obtain the segment upload after the upload_id is sorted by creation time.

If the user only wants to get the segment that an object has uploaded, please refer to [API Docs] (https://docsv4.qingcloud.com/user_guide/storage/object_storage/api/object/multipart/list/).

Request Parameters

You can add some filter options when list multipart uploads.

You can set options below in ListMultipartUploadsInput. See controlled API Docs.

Parameter name Type Description Required
prefix String Limits the response to keys that begin with the specified prefix. No
delimiter Char A delimiter is a character you use to group keys.
If you specify a prefix, all keys that contain the same string between the prefix and the first occurrence of the delimiter after the prefix are grouped under a single result element called CommonPrefixes.		 No
key_marker String Together with upload-id-marker, this parameter specifies the multipart upload after which listing should begin.
If upload-id-marker is not specified, only the keys lexicographically greater than the specified key-marker will be included in the list.
If upload-id-marker is specified, any multipart uploads for a key equal to the key-marker might also be included, provided those multipart uploads have upload IDs lexicographically greater than the specified upload-id-marker.		 No
upload_id_marker String Together with key-marker, specifies the multipart upload after which listing should begin. If key-marker is not specified, the upload-id-marker parameter is ignored. Otherwise, any multipart uploads for a key equal to the key-marker might be included in the list only if they have an upload ID lexicographically greater than the specified upload-id-marker. No
limit Integer Sets the maximum number of objects returned in the response body. Default is 200, maximum is 1000. No

Code Snippet

Initialize the Qingstor object with your AccessKeyID and SecretAccessKey.

from qingstor.sdk.service.qingstor import QingStor
from qingstor.sdk.config import Config

config = Config('ACCESS_KEY_ID_EXAMPLE', 'SECRET_ACCESS_KEY_EXAMPLE')
qingstor = QingStor(config)

Initialize a Bucket object according to the bucket name you set for subsequent creation:

bucket_name = "your-bucket-name"
zone_name = "pek3b"
bucket_srv = qingstor.Bucket(bucket_name, zone_name)

After the object is created, we need to perform a real List Multipart Uploads operation:

The following operations list all objects that have not yet called the Complete MultiUpload interface under the Movies directory (without subdirectories and their files), limited to six.

resp = bucket_srv.list_multipart_uploads(delimiter="/", limit=str(6), prefix="Movies/")
if resp.status_code != 200:
    print("List objects(multiUploaded and the complete api not been called) "
          "of bucket({}) failed with given message: {}".format(bucket_name, str(resp.content, 'utf-8')))
else:
    print(resp['uploads'])