whua3 commented on code in PR #11713:
URL: https://github.com/apache/gravitino/pull/11713#discussion_r3487752990


##########
docs/fileset-catalog-with-cos.md:
##########
@@ -0,0 +1,548 @@
+---
+title: "Fileset Catalog with COS"
+slug: "/fileset-catalog-with-cos"
+date: 2026-06-17
+keyword: "Fileset catalog COS Tencent"
+license: "This software is licensed under the Apache License version 2."
+---
+
+## Introduction
+
+This document explains how to configure a Fileset catalog with Tencent Cloud 
COS (Cloud Object Storage) in Gravitino.
+
+## Prerequisites
+
+To set up a Fileset catalog with COS, follow these steps:
+
+1. Download the 
[`gravitino-tencent-bundle-${gravitino-version}.jar`](https://mvnrepository.com/artifact/org.apache.gravitino/gravitino-tencent-bundle)
 file.
+2. Place the downloaded file into the Gravitino Fileset catalog classpath at 
`${GRAVITINO_HOME}/catalogs/fileset/libs/`.
+3. Start the Gravitino server by running the following command:
+
+```bash
+$ ${GRAVITINO_HOME}/bin/gravitino-server.sh start
+```
+
+Once the server is up and running, you can proceed to configure the Fileset 
catalog with COS. In the rest of this document we will use 
`http://localhost:8090` as the Gravitino server URL, replace with your actual 
server URL.
+
+## COS Catalog Configuration
+
+### COS Fileset Catalog Configuration
+
+In addition to the basic configurations mentioned in 
[Fileset-catalog-catalog-configuration](./fileset-catalog.md#catalog-properties),
 the following properties are required to configure a Fileset catalog with COS:
+
+| Configuration item            | Description                                  
                                                                                
                                                                                
                                                                                
                                                              | Default value | 
Required | Since version |
+|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|----------|---------------|
+| `cos-region`                  | The region of the Tencent Cloud COS bucket, 
e.g. `ap-guangzhou`, `ap-shanghai`.                                             
                                                                                
                                                                                
                                                               | (none)        
| Yes      | 1.4.0         |
+| `cos-endpoint`                | The endpoint *suffix* of the Tencent Cloud 
COS service (mapped to `fs.cosn.bucket.endpoint_suffix`). It is a host suffix, 
not a full URL — e.g. `cos.ap-guangzhou.myqcloud.com`, **not** 
`https://cos.ap-guangzhou.myqcloud.com`. Optional; when not set, hadoop-cos 
derives it from `cos-region` (`cos.${region}.myqcloud.com`). Set this only if 
you need to point to a non-public endpoint (e.g. an internal/VPC endpoint).     
                                                                                
                           | (none)        | No       | 1.4.0         |
+| `cos-access-key-id`           | The static access key ID (Tencent Cloud 
`SecretId`) used to access COS data.                                            
                                                                                
                                                                                
                                                                   | (none)     
   | Yes      | 1.4.0         |
+| `cos-secret-access-key`       | The static secret access key (Tencent Cloud 
`SecretKey`) used to access COS data.                                           
                                                                                
                                                                                
                                                               | (none)        
| Yes      | 1.4.0         |
+| `credential-providers`        | The credential provider types, separated by 
comma. The currently supported value is `cos-secret-key`. Setting this enables 
credential vending provided by the Gravitino server, so the GVFS client no 
longer needs `cos-access-key-id` / `cos-secret-access-key` locally. See 
[cos-credential-vending](#fileset-with-credential-vending) below for details. | 
(none)        | No       | 1.4.0         |
+
+:::note
+The fileset catalog automatically loads filesystem providers on the classpath. 
The COS provider is registered when the `gravitino-tencent-bundle` jar is 
present, so `default-filesystem-provider` and `filesystem-providers` do not 
need to be set.
+:::
+
+:::note
+`cos-region` is mandatory for hadoop-cos: signing requests, building the 
default endpoint and selecting the right CAM scope all require the region. Even 
if you also set `cos-endpoint`, please keep `cos-region` set.

Review Comment:
   done



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to