You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I recently wrote a PR for #7510 that was wrong. So this is rectifying that.
I had used TimestampMillis for a time value that does not have a date, which is wrong.
I've added two new Fields for the missing concept of "time without date", and fixed the conversion to use them, and added the required trait implementations
To Reproduce
Try to parse a TIME_MILLIS parquet value using current main
Expected behavior
You get a field holding the number of milliseconds since midnight, but instead you'll get a field holding the number of milliseconds since epoch.
The text was updated successfully, but these errors were encountered:
Describe the bug
I recently wrote a PR for #7510 that was wrong. So this is rectifying that.
I had used
TimestampMillis
for a time value that does not have a date, which is wrong.I've added two new
Field
s for the missing concept of "time without date", and fixed the conversion to use them, and added the required trait implementationsTo Reproduce
Try to parse a
TIME_MILLIS
parquet value using current mainExpected behavior
You get a field holding the number of milliseconds since midnight, but instead you'll get a field holding the number of milliseconds since epoch.
The text was updated successfully, but these errors were encountered: