tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary
DokumentasiCloud Object StorageUser GuideBatch OperationPerforming Batch OperationBatch Delete Objects

Batch Delete Objects

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-12-10 17:14:59
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:
Operation
List 1 (Keep Current Version Only)
Inventory 2 (Listing Historical Versions)
delete operation
without versionid
with versionid
Versioning not enabled
permanent deletion
permanent deletion
Versioning enabled
Adding a delete marker does not result in permanent deletion.
Performing permanent deletion using the versionid
Suspending Versioning
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
Topik sebelumnya: Batch Restoring Archived ObjectsTopik selanjutnya: Managing Batch Operation Jobs

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan