mzabaluev opened a new issue, #9279:
URL: https://github.com/apache/arrow-rs/issues/9279
**Is your feature request related to a problem or challenge? Please describe
what you are trying to do.**
The logical Avro types to represent an UTC timestamp, e.g.
"timestamp-millis", "timestamp-micros", etc., are represented with Arrow
datatypes specifying the UTC offset ID. Currently the "+00:00" explicit offset
is hardcoded to represent the timestamp types, so e.g. "timestamp-micros" is
mapped to `DataType::Timestamp(TimeUnit::Microseconds, Some("+00:00"))`. This
may cause interoperability problems with applications using the "UTC" timezone
ID, because unfortunately Arrow datatypes using these IDs are not equal.
**Describe the solution you'd like**
Make the timezone ID used to map Avro timestamps configurable in the
`ReaderBuilder` API.
**Describe alternatives you've considered**
Persuade arrow-rs developers to:
- change the representation of time zones to remove the ambiguity;
- make the timestamp datatypes compare equal if they only differ in "UTC"
vs. "+00:00" as the timezone ID.
These changes would break either the API or the behavior of arrow-rs in
general and so would take a lot of time and coordination to implement.
--
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]
