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

Datafusion should not strip out timezone information from existing types #1454

Closed
maxburke opened this issue Dec 16, 2021 · 1 comment · Fixed by #1455
Closed

Datafusion should not strip out timezone information from existing types #1454

maxburke opened this issue Dec 16, 2021 · 1 comment · Fixed by #1455
Labels
bug Something isn't working datafusion Changes in the datafusion crate

Comments

@maxburke
Copy link
Contributor

The Datafusion scalar type does not carry with it any timezone information that may exist in the input data. This leads to queries where the data has a timezone set stripping it out in the results.

@alamb
Copy link
Contributor

alamb commented Dec 16, 2021

I plan to review this carefully tomorrow

@alamb alamb added the datafusion Changes in the datafusion crate label Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working datafusion Changes in the datafusion crate
Projects
None yet
2 participants