zilto commented on issue #47043: URL: https://github.com/apache/arrow/issues/47043#issuecomment-3054369459
@rok Thanks for the quick reply! Indeed, supporting offsets would be useful. I'm a maintainer for the Python library `dlt` and my practical goal is to be able to use `connector-x` as a dependency. This library uses the Rust crate `arrow` and brings significant performance improvements. However, `connector-x` was dealing with [a bug](https://github.com/sfu-db/connector-x/issues/735) with `UTC` timezones which appear to be [unsupported in the Rust crate](https://docs.rs/arrow/latest/arrow/datatypes/enum.DataType.html#variant.Timestamp). > The time zone is a string indicating the name of a time zone, one of: > > As used in the Olson time zone database (the “tz database” or “tzdata”), such as “America/New_York” > An absolute time zone offset of the form +XX:XX or -XX:XX, such as +07:30 They switched to offset-based timezones, which solved their bug, but created downstream issues for some `dlt` users. Given what you know, do you think that `connector-x` adopting `tzdata` format instead of offsets or UTC could be a lasting solution? For instance, `Africa/Bissau` seems to match UTC or +00:00 (could be facing daylight saving time issues?). Alternatively, I could modify `dlt` code to any `+00:00` offsets into UTC Many thanks! -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
