Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arrow Encoding for LocalDate and LocalTime #5446

Merged
merged 4 commits into from
May 3, 2024

Conversation

nbauernfeind
Copy link
Member

Fixes #4823.
Fixes #5265.

niloc132
niloc132 previously approved these changes May 2, 2024
@nbauernfeind nbauernfeind requested a review from jmao-denver May 2, 2024 17:20
Copy link
Contributor

@jmao-denver jmao-denver left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing the changes in arrow.py

rcaudy
rcaudy previously approved these changes May 3, 2024
@nbauernfeind nbauernfeind enabled auto-merge (squash) May 3, 2024 20:14
Comment on lines -109 to -110
pa.date32(),
pa.timestamp('ns', tz='MST'),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like that we don't support pa.timestamp(ns) with a tz, what about just no tz or tz=utc? If we flatly don't support pa.timestamp, maybe we should remove the 'java.time.Instant' mapping?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually the test might be passing now. I suspect the test isn't looking at the time zones. I do think that the data is correct; the timezone is just like a display that applies to all elements. Instant's aren't in a particular time zone in general. Locally I only get lfs and postgres failures; so... we'll find out soon.

@nbauernfeind nbauernfeind merged commit 43d8acf into deephaven:main May 3, 2024
14 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators May 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants