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

date32 fields (days since 1970-01-01) are converted into timestamp fields #86

Open
tom-webber opened this issue Aug 23, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@tom-webber
Copy link

The current handling of date type columns by metadata schema means that fields specified as date32 (days since 1970-01-01) are converted into timestamp fields, when they should be date fields. No extra precision is gained by adding the timestamp, and may cause mismatch if the desired output is truncation of the timestamp to date.

A proposed solution would be to create a table_schema_2.json or equivalent with the addition of a date type_category for date32 fields. This should then become the default for tables going forward.

@tom-webber tom-webber added the bug Something isn't working label Aug 23, 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
Projects
None yet
Development

No branches or pull requests

1 participant