FANNG1 opened a new pull request, #4094: URL: https://github.com/apache/doris-website/pull/4094
## Summary Documents the Alibaba Cloud OSS support added by apache/doris#67157 (issue apache/doris#67131). The Lance catalog page currently tells users that a warehouse can only be a local path, `file://` or `s3://`, so OSS looks unsupported. Requested by @zhangstar333 in apache/doris#67157. ## Changes Both `versioned_docs/version-4.x/.../lance-catalog.mdx` and the zh-CN copy: - `warehouse` now lists `oss://` among the accepted forms. - New **Use Alibaba Cloud OSS** section next to the existing S3 one, with a `CREATE CATALOG` example, the qualified `oss://bucket.oss-<region>.aliyuncs.com/path` form Doris reduces to the bucket, the bucket requirement, and notes on `oss.session_token` and `oss.use_path_style`. - REST catalog section now names the OSS properties usable as defaults, states that namespace-vended credentials take precedence over the catalog's own, and shows a catalog created with no access key at all. - Documents that a namespace may vend the options as either `oss_endpoint` / `oss_access_key_id` / `oss_secret_access_key` / `oss_region` / `oss_security_token` or the bare OSS-native `endpoint` / `access_key_id` / `access_key_secret` / `region` / `security_token`, and that vending one option under both spellings with different values is an error. ## Verification The examples were run against a real OSS bucket on a Doris cluster built from apache/doris#67157, not written from the code alone: - the filesystem example **exactly as written** — without `fs.oss.support`, which the doc does not mention — creates the catalog and scans correctly; - the qualified `oss://bucket.<endpoint>/path` warehouse also scans, and `oss:/path` is rejected at `CREATE CATALOG`; - the no-credential REST example was exercised against a real Apache Gravitino 1.3.0 `lance-rest` service, which vends the bare OSS-native spellings; - the conflicting-spelling error was reproduced. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
