Hi folks, Some of us are having a discussion about a direction change for Rust Arrow timestamp types, which current support both a resolution field (Ns, Micros, Ms, Seconds) similar to the other language implementations, but also optionally a timezone string field. I believe the timezone field is unique to the Rust implementation, as I don’t find it in the C/C++ and Python docs. At the same time, in reality if the timezone field is non null, this is not well supported at all in the current code. Functions returning timestamps pretty much all return a null timezone, for example, and don’t allow the timezone to be specified.
The proposal would be to eliminate the timezone field and bring the Rust Arrow timestamp type in line with that of the other language implementations, also simplifying implementation. It seems this is in line with direction of other projects (Parquet, Spark, and most DBs have timestamp types which do not have explicit timezones or are implicitly UTC). Please feel free to see https://github.com/apache/arrow-datafusion/issues/686 <https://github.com/apache/arrow-datafusion/issues/686> (Or would it be better to discuss here in mailing list?) Cheers! Evan
