Configuring Auto ZIP File Decompression in the Console
Focus Mode
Font Size
Last updated: 2024-11-19 11:55:37
Overview
The ZIP decompression feature is a data processing solution provided by Tencent Cloud COS based on Serverless Cloud Function. When you upload a compressed file to a bucket with a ZIP decompression rule configured, the SCF preset by COS will be triggered automatically to decompress the file into the specified bucket and directory. The decompression flow is as shown below:
You can use the ZIP decompression feature in the following methods:
Console: ZIP files uploaded to the bucket will be automatically decompressed after you configure a ZIP decompression function in the console.
API: You can call the API to trigger the ZIP decompression operation.
This document describes how to decompress ZIP files in the console. For detailed directions on how to use API to decompress ZIP files, see Using API to Decompress ZIP Files.
Notes
ZIP decompression supports decompressing ZIP files.
If you have added a ZIP decompression rule to your bucket in the COS console, you can view the created ZIP decompression function in the SCF console. Do not delete the function; otherwise, your rule may not take effect.
Regions where SCF is available support ZIP decompression, including Guangzhou, Shanghai, Beijing, Chengdu, Hong Kong (China), Singapore and Silicon Valley. For more supported regions, see Serverless Cloud Function.
The directory or file name in your package must be UTF-8 or GB 2312 encoded; otherwise, the directory or file name might be garbled after decompression, or the decompression may be interrupted. If an error is reported, you can click View Log on the right of the function to redirect to the SCF console to view log details.
The decompression service is not supported for files stored in the ARCHIVE storage class. To decompress a package stored in the ARCHIVE storage class, restore it first. For detailed directions, see Restoring Archived Objects.
The maximum processing time for decompressing a compressed file is 900 seconds, beyond which the decompression task will fail. Limits of the COS file decompression feature are subject to SCF. For more limits, see Quota Limits.
The ZIP decompression feature depends on the SCF service which provides a free tier. You will be billed for the part exceeding the free tier according to Pricing. With decompression, the larger your package, the more your resource usage; the more often you decompress packages, the more invocations you will need to use.
4. Select Function Service on the left sidebar and click ZIP Decompression Function.
Note:
If you haven't activated the SCF service, go to the SCF console to activate it and authorize the service as instructed.
5. Click Add Function and configure the following parameters:
Function Name: It uniquely identifies a function and cannot be modified after it is created. You can view the function in the SCF console.
Event Type: An event is an operation that triggers SCF. Take upload as an example. You can initiate an upload by calling the PUT Object or POST Object API. If you select Create using Put method as the event type, decompression will be triggered only by a package uploaded via the PUT Object API.
Note:
If you intend to upload files to the bucket in multiple ways, such as simple upload, multipart upload, and cross-region replication, we recommend you select File upload as the event type.
Trigger Condition: The upload path that will trigger SCF. If you select Specified prefix, SCF will be triggered only when the package is uploaded to a path with the specified prefix. If you select Not specifying prefix, SCF will be triggered as long as a package is uploaded to any location of the bucket.
Note:
If the destination file prefix configured overlaps with the trigger condition, a loop may be triggered, which should be avoided. For example, if the destination file prefix is prefix, and the trigger condition is pre, a decompression loop will be triggered when you upload a pref package.
SCF Authorization: This authorization is required, because decompression requires you to authorize SCF to read the package from your bucket and upload the decompressed files to the specified location.
6. Click Next and configure the following in the pop-up window:
Destination bucket: A bucket to store the decompressed files.
Destination path: Decompress the matched files into this destination directory. To prevent unnecessary fees from triggering the loop, we recommend you set a destination directory different from the prefix.
Extra prefix:
Compressed package name: Decompresses the package to a directory named the same as the package itself.
Package directory: Decompresses the package to a directory named the same as the directory of the package.
Full path of compressed package: Decompresses the package to a prefix that is named the complete path of the package.
Empty: The files in the compressed package will be directly unzip to the delivery path.
Note:
Example:
Upload the 123 package to the test directory of the bucket1-125000000 bucket and then decompress the package to the root directory of the bucket2-1250000000 destination bucket. If you have set one of the following extra prefixes, the delivery path of the files after decompression will be as follows:
Compressed package name: bucket2-1250000000/123
Package directory: bucket2-1250000000/test
Full path of compressed package: bucket2-1250000000/test/123
Empty: bucket2-1250000000
Forbid recursive triggering: Enable does not continue to decompress ZIP packages that are decompressed from the package, while Disable does.
Callback URL: Enter the callback URL as needed.
7. Click Confirm.
You can perform the following operations on the created function:
Click Log to view the historical running status of the ZIP decompression. If an error is reported, you can click Log to quickly redirect to the SCF console to view the error log details.
Click Details to view the ZIP decompression configuration rule.
Click More > Edit to modify the ZIP decompression rule.
Click More > Delete to delete the ZIP decompression rule.
