CurtHagenlocher commented on issue #36558: URL: https://github.com/apache/arrow/issues/36558#issuecomment-3067534989
> If you're dealing with a column that has a uniform, fixed offset time, that shouldn't be forbidden. Mixed offsets and/or mixed timezones are, I believe, a separate problem. In fact, I would go as far as to suggest Arrow might want to add a fourth timestamp format, which would see the internal representation normalized to UTC (as with the other two tz-aware formats) and the tz string in the column metadata pointing to a separate column containing the timezone names or fixed offsets. I think it would make more sense to do this as a struct where one field has the time normalized to UTC and the other has the time zone and/or offset. This is related to #44248. -- 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
