GH-44248: [Format] Add TimestampWithOffset canonical extension type by serramatutu · Pull Request #48002 · apache/arrow

serramatutu · 2025-10-30T11:25:53Z

Rationale for this change

Arrow has no built-in canonical way of representing the TIMESTAMP WITH TIME ZONE SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new arrow.timestamp_with_offset extension type would introduce a standard canonical way of representing that information.

Rust implementation: apache/arrow-rs#8743
Go implementation: apache/arrow-go#558

[DISCUSS] thread in the mailing list.

What changes are included in this PR?

Proposal and documentation for arrow.timestamp_with_offset canonical extension type.

Are these changes tested?

N/A

Are there any user-facing changes?

Yes, this is an extension to the arrow format.

GitHub Issue: [Format] Support an official "timestamp with time zone offset" type #44248

github-actions · 2025-11-20T16:23:43Z

⚠️ GitHub issue #44248has been automatically assigned in GitHub to PR creator.

- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb

Thanks for this PR @serramatutu -- the basic idea looks good to me

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

conbench-apache-arrow · 2025-12-19T13:18:36Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b10386e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 11 possible false positives for unstable benchmarks that are known to sometimes produce them.

# Which issue does this PR close? Implement `arrow.timestamp_with_offset` canonical extension type. # Rationale for this change Be compliant with Arrow spec: apache/arrow#48002 # What changes are included in this PR? This commit adds a new `TimestampWithOffset` extension type. This type represents a timestamp column that stores potentially different timezone offsets per value. The timestamp is stored in UTC alongside the original timezone offset in minutes. # Are these changes tested? Yes. # Are there any user-facing changes? Yes, this is a new canonical extension type.

…type (apache#48002) ### Rationale for this change Closesapache#44248 Arrow has no built-in canonical way of representing the `TIMESTAMP WITH TIME ZONE` SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new `arrow.timestamp_with_offset` extension type would introduce a standard canonical way of representing that information. Rust implementation: apache/arrow-rs#8743 Go implementation: apache/arrow-go#558 [DISCUSS] [thread in the mailing list](https://lists.apache.org/thread/yhbr3rj9l59yoxv92o2s6dqlop16sfnk). ### What changes are included in this PR? Proposal and documentation for `arrow.timestamp_with_offset` canonical extension type. ### Are these changes tested? N/A ### Are there any user-facing changes? Yes, this is an extension to the arrow format. * GitHub Issue: apache#44248 --------- Co-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

serramatutu · 2025-10-30T11:25:53Z

Rationale for this change

Closes#44248

Arrow has no built-in canonical way of representing the TIMESTAMP WITH TIME ZONE SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new arrow.timestamp_with_offset extension type would introduce a standard canonical way of representing that information.

Rust implementation: apache/arrow-rs#8743
Go implementation: apache/arrow-go#558

[DISCUSS] thread in the mailing list.

What changes are included in this PR?

Proposal and documentation for arrow.timestamp_with_offset canonical extension type.

Are these changes tested?

N/A

Are there any user-facing changes?

Yes, this is an extension to the arrow format.

GitHub Issue: [Format] Support an official "timestamp with time zone offset" type #44248

github-actions · 2025-11-20T16:23:43Z

⚠️ GitHub issue #44248has been automatically assigned in GitHub to PR creator.

- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb

Thanks for this PR @serramatutu -- the basic idea looks good to me

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

conbench-apache-arrow · 2025-12-19T13:18:36Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b10386e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 11 possible false positives for unstable benchmarks that are known to sometimes produce them.

# Which issue does this PR close? Implement `arrow.timestamp_with_offset` canonical extension type. # Rationale for this change Be compliant with Arrow spec: apache/arrow#48002 # What changes are included in this PR? This commit adds a new `TimestampWithOffset` extension type. This type represents a timestamp column that stores potentially different timezone offsets per value. The timestamp is stored in UTC alongside the original timezone offset in minutes. # Are these changes tested? Yes. # Are there any user-facing changes? Yes, this is a new canonical extension type.

…type (apache#48002) ### Rationale for this change Closesapache#44248 Arrow has no built-in canonical way of representing the `TIMESTAMP WITH TIME ZONE` SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new `arrow.timestamp_with_offset` extension type would introduce a standard canonical way of representing that information. Rust implementation: apache/arrow-rs#8743 Go implementation: apache/arrow-go#558 [DISCUSS] [thread in the mailing list](https://lists.apache.org/thread/yhbr3rj9l59yoxv92o2s6dqlop16sfnk). ### What changes are included in this PR? Proposal and documentation for `arrow.timestamp_with_offset` canonical extension type. ### Are these changes tested? N/A ### Are there any user-facing changes? Yes, this is an extension to the arrow format. * GitHub Issue: apache#44248 --------- Co-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

serramatutu · 2025-10-30T11:25:53Z

Rationale for this change

Closes#44248

Arrow has no built-in canonical way of representing the TIMESTAMP WITH TIME ZONE SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new arrow.timestamp_with_offset extension type would introduce a standard canonical way of representing that information.

Rust implementation: apache/arrow-rs#8743
Go implementation: apache/arrow-go#558

[DISCUSS] thread in the mailing list.

What changes are included in this PR?

Proposal and documentation for arrow.timestamp_with_offset canonical extension type.

Are these changes tested?

N/A

Are there any user-facing changes?

Yes, this is an extension to the arrow format.

GitHub Issue: [Format] Support an official "timestamp with time zone offset" type #44248

github-actions · 2025-11-20T16:23:43Z

⚠️ GitHub issue #44248has been automatically assigned in GitHub to PR creator.

- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb

Thanks for this PR @serramatutu -- the basic idea looks good to me

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

conbench-apache-arrow · 2025-12-19T13:18:36Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b10386e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 11 possible false positives for unstable benchmarks that are known to sometimes produce them.

# Which issue does this PR close? Implement `arrow.timestamp_with_offset` canonical extension type. # Rationale for this change Be compliant with Arrow spec: apache/arrow#48002 # What changes are included in this PR? This commit adds a new `TimestampWithOffset` extension type. This type represents a timestamp column that stores potentially different timezone offsets per value. The timestamp is stored in UTC alongside the original timezone offset in minutes. # Are these changes tested? Yes. # Are there any user-facing changes? Yes, this is a new canonical extension type.

…type (apache#48002) ### Rationale for this change Closesapache#44248 Arrow has no built-in canonical way of representing the `TIMESTAMP WITH TIME ZONE` SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new `arrow.timestamp_with_offset` extension type would introduce a standard canonical way of representing that information. Rust implementation: apache/arrow-rs#8743 Go implementation: apache/arrow-go#558 [DISCUSS] [thread in the mailing list](https://lists.apache.org/thread/yhbr3rj9l59yoxv92o2s6dqlop16sfnk). ### What changes are included in this PR? Proposal and documentation for `arrow.timestamp_with_offset` canonical extension type. ### Are these changes tested? N/A ### Are there any user-facing changes? Yes, this is an extension to the arrow format. * GitHub Issue: apache#44248 --------- Co-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

serramatutu · 2025-10-30T11:25:53Z

Rationale for this change

Closes#44248

Arrow has no built-in canonical way of representing the TIMESTAMP WITH TIME ZONE SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new arrow.timestamp_with_offset extension type would introduce a standard canonical way of representing that information.

Rust implementation: apache/arrow-rs#8743
Go implementation: apache/arrow-go#558

[DISCUSS] thread in the mailing list.

What changes are included in this PR?

Proposal and documentation for arrow.timestamp_with_offset canonical extension type.

Are these changes tested?

N/A

Are there any user-facing changes?

Yes, this is an extension to the arrow format.

GitHub Issue: [Format] Support an official "timestamp with time zone offset" type #44248

github-actions · 2025-11-20T16:23:43Z

⚠️ GitHub issue #44248has been automatically assigned in GitHub to PR creator.

- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb

Thanks for this PR @serramatutu -- the basic idea looks good to me

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

conbench-apache-arrow · 2025-12-19T13:18:36Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b10386e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 11 possible false positives for unstable benchmarks that are known to sometimes produce them.

# Which issue does this PR close? Implement `arrow.timestamp_with_offset` canonical extension type. # Rationale for this change Be compliant with Arrow spec: apache/arrow#48002 # What changes are included in this PR? This commit adds a new `TimestampWithOffset` extension type. This type represents a timestamp column that stores potentially different timezone offsets per value. The timestamp is stored in UTC alongside the original timezone offset in minutes. # Are these changes tested? Yes. # Are there any user-facing changes? Yes, this is a new canonical extension type.

…type (apache#48002) ### Rationale for this change Closesapache#44248 Arrow has no built-in canonical way of representing the `TIMESTAMP WITH TIME ZONE` SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new `arrow.timestamp_with_offset` extension type would introduce a standard canonical way of representing that information. Rust implementation: apache/arrow-rs#8743 Go implementation: apache/arrow-go#558 [DISCUSS] [thread in the mailing list](https://lists.apache.org/thread/yhbr3rj9l59yoxv92o2s6dqlop16sfnk). ### What changes are included in this PR? Proposal and documentation for `arrow.timestamp_with_offset` canonical extension type. ### Are these changes tested? N/A ### Are there any user-facing changes? Yes, this is an extension to the arrow format. * GitHub Issue: apache#44248 --------- Co-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

serramatutu · 2025-10-30T11:25:53Z

Rationale for this change

Closes#44248

Arrow has no built-in canonical way of representing the TIMESTAMP WITH TIME ZONE SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new arrow.timestamp_with_offset extension type would introduce a standard canonical way of representing that information.

Rust implementation: apache/arrow-rs#8743
Go implementation: apache/arrow-go#558

[DISCUSS] thread in the mailing list.

What changes are included in this PR?

Proposal and documentation for arrow.timestamp_with_offset canonical extension type.

Are these changes tested?

N/A

Are there any user-facing changes?

Yes, this is an extension to the arrow format.

GitHub Issue: [Format] Support an official "timestamp with time zone offset" type #44248

github-actions · 2025-11-20T16:23:43Z

⚠️ GitHub issue #44248has been automatically assigned in GitHub to PR creator.

- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb

Thanks for this PR @serramatutu -- the basic idea looks good to me

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

conbench-apache-arrow · 2025-12-19T13:18:36Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b10386e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 11 possible false positives for unstable benchmarks that are known to sometimes produce them.

# Which issue does this PR close? Implement `arrow.timestamp_with_offset` canonical extension type. # Rationale for this change Be compliant with Arrow spec: apache/arrow#48002 # What changes are included in this PR? This commit adds a new `TimestampWithOffset` extension type. This type represents a timestamp column that stores potentially different timezone offsets per value. The timestamp is stored in UTC alongside the original timezone offset in minutes. # Are these changes tested? Yes. # Are there any user-facing changes? Yes, this is a new canonical extension type.

…type (apache#48002) ### Rationale for this change Closesapache#44248 Arrow has no built-in canonical way of representing the `TIMESTAMP WITH TIME ZONE` SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new `arrow.timestamp_with_offset` extension type would introduce a standard canonical way of representing that information. Rust implementation: apache/arrow-rs#8743 Go implementation: apache/arrow-go#558 [DISCUSS] [thread in the mailing list](https://lists.apache.org/thread/yhbr3rj9l59yoxv92o2s6dqlop16sfnk). ### What changes are included in this PR? Proposal and documentation for `arrow.timestamp_with_offset` canonical extension type. ### Are these changes tested? N/A ### Are there any user-facing changes? Yes, this is an extension to the arrow format. * GitHub Issue: apache#44248 --------- Co-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

serramatutu · 2025-10-30T11:25:53Z

Rationale for this change

Closes#44248

Arrow has no built-in canonical way of representing the TIMESTAMP WITH TIME ZONE SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new arrow.timestamp_with_offset extension type would introduce a standard canonical way of representing that information.

Rust implementation: apache/arrow-rs#8743
Go implementation: apache/arrow-go#558

[DISCUSS] thread in the mailing list.

What changes are included in this PR?

Proposal and documentation for arrow.timestamp_with_offset canonical extension type.

Are these changes tested?

N/A

Are there any user-facing changes?

Yes, this is an extension to the arrow format.

GitHub Issue: [Format] Support an official "timestamp with time zone offset" type #44248

github-actions · 2025-11-20T16:23:43Z

⚠️ GitHub issue #44248has been automatically assigned in GitHub to PR creator.

- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb

Thanks for this PR @serramatutu -- the basic idea looks good to me

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

conbench-apache-arrow · 2025-12-19T13:18:36Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b10386e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 11 possible false positives for unstable benchmarks that are known to sometimes produce them.

# Which issue does this PR close? Implement `arrow.timestamp_with_offset` canonical extension type. # Rationale for this change Be compliant with Arrow spec: apache/arrow#48002 # What changes are included in this PR? This commit adds a new `TimestampWithOffset` extension type. This type represents a timestamp column that stores potentially different timezone offsets per value. The timestamp is stored in UTC alongside the original timezone offset in minutes. # Are these changes tested? Yes. # Are there any user-facing changes? Yes, this is a new canonical extension type.

…type (apache#48002) ### Rationale for this change Closesapache#44248 Arrow has no built-in canonical way of representing the `TIMESTAMP WITH TIME ZONE` SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new `arrow.timestamp_with_offset` extension type would introduce a standard canonical way of representing that information. Rust implementation: apache/arrow-rs#8743 Go implementation: apache/arrow-go#558 [DISCUSS] [thread in the mailing list](https://lists.apache.org/thread/yhbr3rj9l59yoxv92o2s6dqlop16sfnk). ### What changes are included in this PR? Proposal and documentation for `arrow.timestamp_with_offset` canonical extension type. ### Are these changes tested? N/A ### Are there any user-facing changes? Yes, this is an extension to the arrow format. * GitHub Issue: apache#44248 --------- Co-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

serramatutu · 2025-10-30T11:25:53Z

Rationale for this change

Closes#44248

Arrow has no built-in canonical way of representing the TIMESTAMP WITH TIME ZONE SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new arrow.timestamp_with_offset extension type would introduce a standard canonical way of representing that information.

Rust implementation: apache/arrow-rs#8743
Go implementation: apache/arrow-go#558

[DISCUSS] thread in the mailing list.

What changes are included in this PR?

Proposal and documentation for arrow.timestamp_with_offset canonical extension type.

Are these changes tested?

N/A

Are there any user-facing changes?

Yes, this is an extension to the arrow format.

GitHub Issue: [Format] Support an official "timestamp with time zone offset" type #44248

github-actions · 2025-11-20T16:23:43Z

⚠️ GitHub issue #44248has been automatically assigned in GitHub to PR creator.

- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb

Thanks for this PR @serramatutu -- the basic idea looks good to me

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

conbench-apache-arrow · 2025-12-19T13:18:36Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b10386e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 11 possible false positives for unstable benchmarks that are known to sometimes produce them.

# Which issue does this PR close? Implement `arrow.timestamp_with_offset` canonical extension type. # Rationale for this change Be compliant with Arrow spec: apache/arrow#48002 # What changes are included in this PR? This commit adds a new `TimestampWithOffset` extension type. This type represents a timestamp column that stores potentially different timezone offsets per value. The timestamp is stored in UTC alongside the original timezone offset in minutes. # Are these changes tested? Yes. # Are there any user-facing changes? Yes, this is a new canonical extension type.

…type (apache#48002) ### Rationale for this change Closesapache#44248 Arrow has no built-in canonical way of representing the `TIMESTAMP WITH TIME ZONE` SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new `arrow.timestamp_with_offset` extension type would introduce a standard canonical way of representing that information. Rust implementation: apache/arrow-rs#8743 Go implementation: apache/arrow-go#558 [DISCUSS] [thread in the mailing list](https://lists.apache.org/thread/yhbr3rj9l59yoxv92o2s6dqlop16sfnk). ### What changes are included in this PR? Proposal and documentation for `arrow.timestamp_with_offset` canonical extension type. ### Are these changes tested? N/A ### Are there any user-facing changes? Yes, this is an extension to the arrow format. * GitHub Issue: apache#44248 --------- Co-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

serramatutu · 2025-10-30T11:25:53Z

Rationale for this change

Closes#44248

Arrow has no built-in canonical way of representing the TIMESTAMP WITH TIME ZONE SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new arrow.timestamp_with_offset extension type would introduce a standard canonical way of representing that information.

Rust implementation: apache/arrow-rs#8743
Go implementation: apache/arrow-go#558

[DISCUSS] thread in the mailing list.

What changes are included in this PR?

Proposal and documentation for arrow.timestamp_with_offset canonical extension type.

Are these changes tested?

N/A

Are there any user-facing changes?

Yes, this is an extension to the arrow format.

GitHub Issue: [Format] Support an official "timestamp with time zone offset" type #44248

github-actions · 2025-11-20T16:23:43Z

⚠️ GitHub issue #44248has been automatically assigned in GitHub to PR creator.

- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb

Thanks for this PR @serramatutu -- the basic idea looks good to me

Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

conbench-apache-arrow · 2025-12-19T13:18:36Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b10386e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 11 possible false positives for unstable benchmarks that are known to sometimes produce them.

# Which issue does this PR close? Implement `arrow.timestamp_with_offset` canonical extension type. # Rationale for this change Be compliant with Arrow spec: apache/arrow#48002 # What changes are included in this PR? This commit adds a new `TimestampWithOffset` extension type. This type represents a timestamp column that stores potentially different timezone offsets per value. The timestamp is stored in UTC alongside the original timezone offset in minutes. # Are these changes tested? Yes. # Are there any user-facing changes? Yes, this is a new canonical extension type.

…type (apache#48002) ### Rationale for this change Closesapache#44248 Arrow has no built-in canonical way of representing the `TIMESTAMP WITH TIME ZONE` SQL type, which is present across multiple different database systems. Not having a native way to represent this forces users to either convert to UTC and drop the time zone, which may have correctness implications, or use bespoke workarounds. A new `arrow.timestamp_with_offset` extension type would introduce a standard canonical way of representing that information. Rust implementation: apache/arrow-rs#8743 Go implementation: apache/arrow-go#558 [DISCUSS] [thread in the mailing list](https://lists.apache.org/thread/yhbr3rj9l59yoxv92o2s6dqlop16sfnk). ### What changes are included in this PR? Proposal and documentation for `arrow.timestamp_with_offset` canonical extension type. ### Are these changes tested? N/A ### Are there any user-facing changes? Yes, this is an extension to the arrow format. * GitHub Issue: apache#44248 --------- Co-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

github-actionsBot added the Component: Documentation label Oct 30, 2025

serramatutu mentioned this pull request Oct 30, 2025
Add TimestampWithOffset canonical extension type apache/arrow-go#558
Merged

github-actionsBot added the awaiting review Awaiting review label Oct 30, 2025

serramatutu mentioned this pull request Oct 30, 2025
Add TimestampWithOffset canonical extension type apache/arrow-rs#8743
Merged

serramatutu changed the title ~~[FORMAT] Add Timestamp With Offset canonical extension type~~[DRAFT][FORMAT] Add Timestamp With Offset canonical extension typeOct 30, 2025

Add Timestamp With Offset canonical extension type
fe8056f

serramatutu force-pushed the serramatutu/TimestampWithOffset/format branch from 14fd59a to fe8056fCompare October 30, 2025 12:30

rok reviewed Oct 30, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

CurtHagenlocher mentioned this pull request Oct 30, 2025
[Format] Support an official "timestamp with time zone offset" type #44248
Closed

jorisvandenbossche reviewed Oct 30, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

jorisvandenbossche reviewed Oct 30, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

github-actionsBot added awaiting changes Awaiting changes awaiting committer review Awaiting committer review and removed awaiting review Awaiting review awaiting committer review Awaiting committer review awaiting changes Awaiting changes labels Oct 31, 2025

rok requested review from lidavidm and zeroshade October 31, 2025 13:21

lidavidm reviewed Nov 3, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated
Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

serramatutu added 2 commits November 3, 2025 14:19

fixe: move timestamp offset to its own section
080220a

Add note about compat with ANSI SQL
d8b900f

github-actionsBot added awaiting change review Awaiting change review and removed awaiting changes Awaiting changes labels Nov 3, 2025

serramatutu commented Nov 5, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

serramatutu force-pushed the serramatutu/TimestampWithOffset/format branch from d40c0bb to b0d9be3Compare November 20, 2025 08:52

serramatutu added 3 commits November 20, 2025 14:34

Typos
018b5e8

Felipe's suggestion
5c3a3a8

Make dict and REE section more concise
d4d50b3

serramatutu force-pushed the serramatutu/TimestampWithOffset/format branch from 6ab0deb to d4d50b3Compare November 20, 2025 14:30

pitrou reviewed Nov 20, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

pitrou reviewed Nov 20, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

pitrou reviewed Nov 20, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

felipecrv changed the title ~~[DRAFT][FORMAT] Add Timestamp With Offset canonical extension type~~GH-44248: [FORMAT] Add TimestampWithOffset canonical extension typeNov 20, 2025

apache deleted a comment from github-actionsBotNov 20, 2025

Implement Pitrou's suggestion
043b07c
- Drop JSON encoding recommendation - Inner fields must be non-nullble - Time unit is not a type parameter

alamb reviewed Nov 21, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst

alamb reviewed Nov 21, 2025
View reviewed changes

felipecrv marked this pull request as ready for review November 24, 2025 17:17

github-actionsBot added awaiting changes Awaiting changes and removed awaiting change review Awaiting change review labels Nov 25, 2025

jorisvandenbossche approved these changes Nov 25, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

wgtmac reviewed Nov 25, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

github-actionsBot added awaiting merge Awaiting merge and removed awaiting changes Awaiting changes labels Nov 25, 2025

Formatting
7b35e5b
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>

felipecrv approved these changes Nov 25, 2025
View reviewed changes

Comment threaddocs/source/format/CanonicalExtensions.rst Outdated

Reword offsets
c73ec56
Co-authored-by: Felipe Oliveira Carvalho <felipekde@gmail.com>

pitrou changed the title ~~GH-44248: [FORMAT] Add TimestampWithOffset canonical extension type~~GH-44248: [Format] Add TimestampWithOffset canonical extension typeNov 26, 2025

felipecrv merged commit b10386e into apache:mainDec 5, 2025
7 checks passed