Add TimestampWithOffset extension type
#8743
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
westonpace
approved these changes
Nov 4, 2025
Member
westonpace
left a comment
westonpace
left a comment
There was a problem hiding this comment.
This seems pretty straightforward and reasonable
alamb
changed the title
TimestampWithOffset extension typeTimestampWithOffset extension type
Contributor
|
There are several TODOs in this PRs description. Is that intended? |
Author
|
@alamb We're currently still discussing the FORMAT in the For
Realistically, even after the FORMAT PR goes into the spec I think this will take me a few more weeks to fully flesh out. |
Contributor
|
Thanks for the clarification @serramatutu -- I'll mark it as a draft again then |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
(TODO: create Github Issue if the [VOTE] succeeds)
(TODO: does
arrow-rshave a way to serialize this as RFC3339 instead of struct when going to/from JSON?)No issue yet. This is still being discussed in the mailing list, and this PR is here for reference.
FORMAT Pull request: apache/arrow#48002
Rationale for this change
Please refer to the mailing list discussion (we'll send an e-mail with the proposal soon).
What changes are included in this PR?
This commit adds a new
TimestampWithOffsetextension 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 proposed canonical extension type.