whua3 commented on issue #6490: URL: https://github.com/apache/gravitino/issues/6490#issuecomment-4692822169
Hi @yuqi1129 , I would like to pick this one up if nobody's working on it yet. Plan is to follow roughly the same path the OSS support took (#5174 → #5701 → #5239 → #5777), splitting the work into the following PRs — open to reordering or merging based on review: - **PR-A** — Java side: `bundles/cos` + `bundles/cos-bundle` + Hadoop catalog wiring + Java GVFS, static AK/SK only. (mirrors #5174) - **PR-B** — Server-side STS credential vending: `COSTokenProvider` + `COSTokenGenerator` + policy DSL. Depends on PR-A. (mirrors #5701) - **PR-C** — Python GVFS support: `COSStorageHandler` in `gvfs_storage_handler.py`, plus `COSSecretKeyCredential`. Depends on PR-A. (mirrors #5239) - **PR-D** — Python `COSTokenCredential` wiring. Depends on PR-B + PR-C. Could fold into PR-C if you'd prefer fewer PRs — happy either way. Iceberg / Paimon support I'd leave for a separate follow-up issue, otherwise the scope gets too big. A few things I'd like to confirm before starting: 1. **Scheme** — planning to use `cosn://` since that's what `hadoop-cos` registers natively. Let me know if there's a reason to prefer something else. 2. **AppID** — Tencent recommends embedding it into the bucket name (`my-bucket-1259999999`), so I wasn't going to add a separate `cos-app-id` property. Sound reasonable? 3. **Python fsspec backend** — planning to use the community [`cosfs`](https://pypi.org/project/cosfs/) package, lazy-imported the same way `ossfs` is. 4. **Integration tests** — planning the same env-var-gated pattern as the OSS ITs (`COS_BUCKET_NAME`, `COS_REGION`, etc.; skipped via `Assumptions.assumeTrue` when absent). Let me know if there's a different expectation for new cloud providers. Will share a draft of PR-A once it's ready. Happy to adjust the split or any of the above based on feedback. -- 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]
