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
This is fixed in #933 , which has been waiting for pandas maintainers' approval for merge. Since a month has passed, I will merge and release it now anyway.
Describe the issue:
When reading timezone aware timestamps data stored with micro-second unit, parquet corrupt them to unix time.
Minimal Complete Verifiable Example:
output:
Anything else we need to know?:
unit="us"
tounit="ns"
works fine.unit="us"
but without timezone works fine as well.Only the combination of the 2 creates the issue.
test.pq
) with another engine (pyarrow
) works fine.The issue seems to comes from the reading part.
Note: I discovered this issue while storing BigQuery data. They are using micro-second (us) timestamps.
Environment:
The text was updated successfully, but these errors were encountered: