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
{{ message }}
Repository navigation
[Python] write_to_dataset, coerce_timestamps issue with stored binary schema #45062
Describe the bug, including details regarding any error messages, version, and platform.
When using coerce_timestamps=us, it seems that the parquet metadata are correclty being set as datetime[us] however, the stored binary arrow schema seems to still be a datetime[ns] creating mismatch of type depending on the engine you use to read the data.
The issue is that store_schema is not supported in the write_to_dataset function as this parameter is not available in ParquetFileWriteOptions but only in the write_table function and ParquetWriter class.
I guess the stored binary arrow schema should be stored with datetime[us] instead of datetime[ns] when using coerce_timestamps parameter but the store_schema parameter should also be made available to the write_to_dataset function
changed the title [-]write_to_dataset, coerce_timestamps issue with stored binary schema[/-][+][Python] write_to_dataset, coerce_timestamps issue with stored binary schema[/+]on Dec 19, 2024
Activity
[-]write_to_dataset, coerce_timestamps issue with stored binary schema[/-][+][Python] write_to_dataset, coerce_timestamps issue with stored binary schema[/+]tadeja commentedon Sep 25, 2026
Note that (workaround) part of this issue -
store_schemanot getting accepted bywrite_to_dataset- would be fixed with #51461 / PR #51461.And the main part of schema inconsistency is likely duplicating this issue: #47336