This is an automated email from the ASF dual-hosted git repository.
yuqi1129 pushed a commit to branch branch-1.3
in repository https://gitbox.apache.org/repos/asf/gravitino.git
The following commit(s) were added to refs/heads/branch-1.3 by this push:
new 27affe019a [Cherry-pick to branch-1.3] [#11077] docs: Document Trino
482 fix for SHOW SCHEMAS on Gravitino IRC (#11808) (#11823)
27affe019a is described below
commit 27affe019afd15b02bdc8f046f7d6b0485e94a6e
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Jun 29 22:45:11 2026 +0800
[Cherry-pick to branch-1.3] [#11077] docs: Document Trino 482 fix for SHOW
SCHEMAS on Gravitino IRC (#11808) (#11823)
**Cherry-pick Information:**
- Original commit: ae9a52191f1902377aa6304db1af07ccc3462b37
- Target branch: `branch-1.3`
- Status: ✅ Clean cherry-pick (no conflicts)
Co-authored-by: MaSai <[email protected]>
---
docs/iceberg-rest-engine/trino.md | 20 +++++++++++++++-----
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/docs/iceberg-rest-engine/trino.md
b/docs/iceberg-rest-engine/trino.md
index 0302314b49..2a438830d6 100755
--- a/docs/iceberg-rest-engine/trino.md
+++ b/docs/iceberg-rest-engine/trino.md
@@ -190,14 +190,24 @@ WITH (
## Known Issues
+### `SHOW SCHEMAS` Fails on Gravitino IRC (OAuth2, Nested Namespaces)
+
+**Cause:** When Trino connects to Gravitino IRC with
`iceberg.rest-catalog.security=OAUTH2`,
+`iceberg.rest-catalog.nested-namespace-enabled=true`, and
`iceberg.rest-catalog.session=NONE`
+(the default), `SHOW SCHEMAS` recursively calls Iceberg REST `listNamespaces`.
On Trino releases
+before 482, each recursive call creates a separate OAuth session, which can
trigger excessive token
+requests and cause errors such as `Connection pool shut down` or
`StackOverflowError`.
+
+**Solution:** Upgrade to Trino 482+.
+
### `TIMESTAMP WITH TIME ZONE` Values Are Not Adjusted to the Client Session
Time Zone
-For `TIMESTAMP WITH TIME ZONE` values, Trino does not adjust query results
according to the client
-session time zone. Unlike Spark and Flink, Trino displays these values based
on the stored
-timestamp-with-time-zone value.
+**Cause:** For `TIMESTAMP WITH TIME ZONE` values, Trino does not adjust query
results according to
+the client session time zone. Unlike Spark and Flink, Trino displays these
values based on the
+stored timestamp-with-time-zone value.
-To convert a `TIMESTAMP WITH TIME ZONE` value to the current client session
time zone, use
-`at_timezone` together with `current_timezone()`:
+**Solution:** To convert a `TIMESTAMP WITH TIME ZONE` value to the current
client session time
+zone, use `at_timezone` together with `current_timezone()`:
```sql
SELECT
