From 0d7cfd3a4c2818d5e6e2d8bd185eb5dcfa874219 Mon Sep 17 00:00:00 2001 From: Marcin Rusek Date: Wed, 8 Oct 2025 09:45:38 +0200 Subject: [PATCH 1/2] Add a known limitation of ORC reader to docs. --- docs/src/main/sphinx/object-storage/file-formats.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/src/main/sphinx/object-storage/file-formats.md b/docs/src/main/sphinx/object-storage/file-formats.md index 046d821984a8..0ecfbeb91402 100644 --- a/docs/src/main/sphinx/object-storage/file-formats.md +++ b/docs/src/main/sphinx/object-storage/file-formats.md @@ -31,6 +31,13 @@ with ORC files performed by supported object storage connectors: [](file-compression) is automatically performed and some details can be configured. +Limitations: +[Trino ignores Calendar entry in ORC file metadata.](https://github.com/trinodb/trino/issues/26865) +As a result Trino always treats dates and timestamps as values written using +proleptic Gregorian calendar. This causes incorrect values read when reading +date/time values before Oct 15, 1582 that were written using hybrid +Julian-Gregorian calendar. + (parquet-format-configuration)= ## Parquet format configuration properties From 904f303de6fbeb19a58552f225d62e27439792ab Mon Sep 17 00:00:00 2001 From: Marcin Rusek Date: Mon, 13 Oct 2025 10:05:39 +0200 Subject: [PATCH 2/2] Add a known limitation of ORC reader to docs. --- docs/src/main/sphinx/object-storage/file-formats.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/src/main/sphinx/object-storage/file-formats.md b/docs/src/main/sphinx/object-storage/file-formats.md index 0ecfbeb91402..c192e6ad5fe9 100644 --- a/docs/src/main/sphinx/object-storage/file-formats.md +++ b/docs/src/main/sphinx/object-storage/file-formats.md @@ -31,7 +31,8 @@ with ORC files performed by supported object storage connectors: [](file-compression) is automatically performed and some details can be configured. -Limitations: +## ORC support limitations + [Trino ignores Calendar entry in ORC file metadata.](https://github.com/trinodb/trino/issues/26865) As a result Trino always treats dates and timestamps as values written using proleptic Gregorian calendar. This causes incorrect values read when reading