diqiu50 opened a new issue, #14069: URL: https://github.com/apache/gravitino/issues/14069
### Version main branch ### Describe what's wrong The Hive catalog has no path-based credential context, so token providers (`s3-token`, `oss-token`, `gcs-token`, `adls-token`, `cos-token`) always return no credentials for it. Only static providers (`s3-secret-key`, `oss-secret-key`, `azure-account-key`) work, which means a Hive catalog cannot vend GCS credentials at all. However: - Creating a Hive catalog with such a provider succeeds without any error. - `docs/security/credential-vending.md` lists Hive as vending S3, OSS, GCS and ADLS. ### Error message and/or stacktrace No error when the catalog is created. Later, engine queries on its tables fail with storage authorization errors. ### How to reproduce 1. Create a Hive catalog on GCS with `credential-providers=gcs-token`. 2. The catalog is created successfully. 3. Queries from Spark/Trino/Flink on its tables fail with storage authorization errors. ### Additional context Expected: - Catalog creation/alteration rejects a token provider the catalog type cannot vend, with an error naming both the provider and the catalog type. - The docs table lists what each catalog type actually vends. -- 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]
