[python]Fix avro write timestamp without timezone wrongly #7259
+19
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
When fastavro writes timestamp without a timezone (such as pyarrow.timestamp('us')), the write and read results will differ by 8 hours.
This is because fastavro calculates the timestamp based on the local timezone (UTC+8) when writing no-timezone datetime data of the timestamp-millis logical type. It subtracts 8 hours when storing UTC timestamp, resulting in an 8-hour difference when reading.
Tests
test_py_write_read_pk_table()
API and Format
Documentation
Generative AI tooling