comphead commented on issue #8336: URL: https://github.com/apache/arrow-datafusion/issues/8336#issuecomment-1828745837
The overflow happens because Datafusion treats underlying `i64` as nanoseconds which is obviously not big enough. Other sql engines like PG/Spark/DuckDB treat `i64` as microsecond. Parquet was using deprecated `i96` datatype to fit the value. Some evident options are: - treat Timestamp `i64` as microsecond, the similar way PG, Spark, DuckDB works. This might involve huge work, as all timestamp conversions, functions expects nanoseconds. - Extend Timestamp underlying value to `i128` instead of `i64` by modifying the code or by conditional compilation. @alamb @waitingkuo @viirya @tustvold would be nice to hear from you -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
