Hello,
For the first time I notice this piece of information about the
timestamp type:
/// * If the time zone is set to a valid value, values can be displayed as
/// "localized" to that time zone, even though the underlying 64-bit
/// integers are identical to the same data stored in UTC. Converting
/// between time zones is a metadata-only operation and does not change the
/// underlying values
(from https://github.com/apache/arrow/blob/master/format/Schema.fbs#L223 )
This seems rather weird to me: timestamps always convey a UTC timestamp
value, optionally decorated with a local timezone? What is the
motivation for such a representation? It is unlike other systems such
as Python, where a timezone-aware timestamp really expresses a local
time value, not a UTC time value.
Thank you,
Antoine.
