Batch delete operation can be used to delete objects in the inventory. For instructions on the delete operation, refer to DELETE Object. The version control status of the bucket affects the execution result of batch delete. For details, refer to version control overview. Note
1. Based on whether the inventory includes the object's versionid, it determines whether the delete request initiated during the batch delete task includes the versionid.
When the inventory only retains the current version, it will perform a delete operation without versionid, namely DELETE /example.txt
When the inventory lists historical versions, it will perform a delete operation with versionid, namely DELETE /example.txt?versionid=xxx
2. When the bucket is in one of three different states—versioning not enabled, versioning suspended, or versioning enabled—a delete operation without versionid will yield different results. However, a delete operation with versionid ensures the object is permanently deleted. For details, refer to Versioning Overview. The behavior of batch deleting objects under different conditions is as follows: |
| | |
| | |
| Adding a delete marker does not result in permanent deletion. | Performing permanent deletion using the versionid |
| Adding a delete marker, if there is a null version object in the bucket, that object will be permanently deleted, and non-null version objects will not be deleted. | Performing permanent deletion using the versionid |