tustvold commented on issue #8899: URL: https://github.com/apache/arrow-datafusion/issues/8899#issuecomment-1900735278
> Incidentally arrow doesn't like that time string so you can't input it anyway Parser error: Error parsing timestamp from '2024-10-27 02:30:00 Europe/Berlin': error computing timezone offset. You have to enable the chrono-tz feature to parse non-offset timezones, it definitely supports them > The more likely thing is to have a stream of input from a machine produced in UTC. If one wants to display the output in a local timezone then one could use a query like > if the earliest is always chosen for the ambiguous cases this would produce results like: I think we should see what postgres does here, I'm not entirely sure what the correct behaviour here is, very little is intuitive or logical when it comes to DST -- 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]
