Docs

Torch Object Storage

Task processing

File decompression

TOS allows you to create tasks to decompress files and then store the decompressed files in a specified bucket. This topic explains how to decompress files and lists the applicable limitations.

tip

File decompression is currently in closed beta. Please contact your account manager for access.

Prerequisites

Before you begin, you must first grant TOS permission to read from and write to the relevant buckets. If you have enabled server-side encryption for the destination bucket, you must also grant TOS permission to access Key Management Service (KMS). TOS will use KMS keys to encrypt files.

The first time you use the file decompression feature, navigate to the File decompression tab on the Task processing page. Then, complete the following steps:

Click Click to Authorize under Grant read/write permissions to give TOS read and write permissions to the bucket.

Click Click to Authorize under Grant KMS permissions to give TOS permission to access KMS.

Notes

Category	Description
QPS	The default file decompression quota is 5 QPS per account in each region. Requests exceeding this quota are throttled, which may result in failed task creation. Reduce the request rate and try again. To increase the QPS quota, submit a ticket to technical support.
File format and decompression method	Currently, only zip archives are supported. TOS uses streaming decompression, writing each file as the archive decompresses. If a corrupted file interrupts this process, TOS retains the files that were successfully decompressed prior to the interruption.
File restrictions	File size: The archive must be less than 100 GB, and each decompressed file must be less than 40 GB. Number of files: An archive may contain no more than 80,000 files. Storage type: Files in Archive, Cold Archive, or Deep Cold Archive cannot be directly decompressed. Restore these files before decompressing them. Files with the same name: If versioning is not enabled for the destination bucket, a decompressed file will overwrite an existing file with the same name. If versioning is enabled for the destination bucket and there is already a file with the same name, the decompressed file becomes the latest version and the existing file becomes a historical version.
Others	TOS cannot decompress encrypted archives.

Billing notes

Using this feature incurs fees for file decompression, requests, and data retrieval. Specifically:

Billable item	Description
File decompression	You are charged based on the size of the decompressed files. For more information, see Data processing.
Requests	TOS sends GetObject requests when reading an archive. When writing the decompressed files, TOS sends PutObject requests. You are charged for these requests. The cost of a request depends on the storage type of the files being requested. For more information, see Requests.
Data retrievals	You are charged based on the amount of data retrieved when you decompress files in Infrequent Access Storage or Flashback Archive. For more information, see Data retrievals.

Steps

In the left navigation pane, click Buckets. In the Buckets list, click the bucket you want to manage.

In the left navigation pane, select Data processing > Task processing.

On the task processing page, click Create task on the File decompression tab.

In the Create task dialog box, configure the following parameters.

Parameter	Description
Main task type	File processing is selected by default.
Subtask type	File decompression is selected by default.
Source file path	Select the archive that you want to decompress. Only archives from the current bucket are available for selection.
Target bucket	Select the bucket where the decompressed files will be stored. tip Currently, you can only store decompressed files in the same region as the source bucket. Therefore, select a destination bucket in the same region.
Target path	Specify the path in the destination bucket where the decompressed files will be stored. If this parameter is left empty, the files will be stored in the root directory of the destination bucket.
Reserved archive name	Select whether to create a folder with the same name as the archive and store the decompressed files in that folder. Use this parameter with the Target path parameter to determine where the decompressed files will be stored. The options are: No: The files in the archive are decompressed to the target path in the format /<target path>/<file name>. Yes: TOS creates a folder with the same name as the archive under the target path and decompresses the files to that folder. The resulting path is /< target path>/<archive name>/<file name>. Preserve the full path of the compressed package: TOS recreates the original archive path under the target path. It creates a folder with the same name as the archive under that path and decompresses the files to the folder. The resulting path is /<target path>/<original archive path>/<archive name>/<file name>. For example, if the original archive path is /bbb/test.zip, the target path is /aaa/, and Preserve the full path of the compressed package is selected, the decompressed files are stored under /aaa/bbb/test/.

Once you have finished configuring, click OK.

After creating the task, verify that the decompressed files appear in the destination bucket. If the files are present, then the decompression task was successful.

Last updated: 2026.10.19 11:17:11