sm-Fifteen commented on issue #36558: URL: https://github.com/apache/arrow/issues/36558#issuecomment-1799532051
> The other thing is that Arrow itself doesn't support timezone identifiers in the Area/Location format anywhere that data is ingested. Neither CSVs, for example, nor the cast support it. That's a whole other issue, you can only get timestamps into Arrow using timezone offsets, but then they're useless, because everywhere you can actually use a timezone it only works with area identifiers. Yeah, unless you store the timezone offset into a separate column (I don't know whether that's possible when using Arrow directly), when loading timestamps from a row-oriented format like CSV, you lose that information when the entire column is normalized. To get a timezone specifier, assigned to the column, you have to know it in advance or disregard the original one and use a "working/display timezone". Even if you could load timestamps from a CSV file with IANA timezones attached to them, like with the [proposed ECMAScript extended timestamp format](https://tc39.es/proposal-temporal/docs/persistence-model.svg), you would have the same problem as with plain offsets, because the issue isn't using or not using tzdb names, it's whether or not the column can be considered to use a single, uniform timezone. -- 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
