This is an automated email from the ASF dual-hosted git repository.
jerryshao pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/gravitino.git
The following commit(s) were added to refs/heads/main by this push:
new 66f7f2cd91 [MINOR] docs: clarify Trino timezone behavior (#11106)
66f7f2cd91 is described below
commit 66f7f2cd913f172cca3201ee3d6b1d257dffc26d
Author: MaSai <[email protected]>
AuthorDate: Mon May 18 10:27:02 2026 +0800
[MINOR] docs: clarify Trino timezone behavior (#11106)
### What changes were proposed in this pull request?
Add a Trino-specific note to `docs/iceberg-rest-engine/trino.md` that
explains how `TIMESTAMP WITH TIME ZONE` values are displayed, why Trino
does not adjust them based on the client session time zone, and how to
convert them with `at_timezone(..., current_timezone())`.
### Why are the changes needed?
Users need explicit guidance on Trino's timezone behavior when querying
timestamp values through the Gravitino Iceberg REST Catalog.
Fixes #11107
### Does this PR introduce _any_ user-facing change?
Yes. The Trino Iceberg REST documentation now explains timezone behavior
for `TIMESTAMP WITH TIME ZONE` values and provides a SQL workaround.
### How was this patch tested?
Documentation update only.
---------
Co-authored-by: Copilot <[email protected]>
---
docs/iceberg-rest-engine/trino.md | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/docs/iceberg-rest-engine/trino.md
b/docs/iceberg-rest-engine/trino.md
index d03bd0b4e8..aeef7425a1 100755
--- a/docs/iceberg-rest-engine/trino.md
+++ b/docs/iceberg-rest-engine/trino.md
@@ -158,6 +158,24 @@ WITH (
);
```
+## Known issues
+
+### `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.
+
+To convert a `TIMESTAMP WITH TIME ZONE` value to the current client session
time zone, use
+`at_timezone` together with `current_timezone()`:
+
+```sql
+SELECT
+ id,
+ at_timezone(timestamp_with_timezone_column, current_timezone())
+FROM <catalog>.<namespace>.<table>;
+```
+
## Gravitino connector vs Iceberg REST
| Feature | Gravitino Engine Connector | Iceberg REST
|