alamb commented on issue #4106: URL: https://github.com/apache/arrow-datafusion/issues/4106#issuecomment-1309040786
> or do we throw errors for ambiguous/invalid timestamps? This would be my preference I think -- no one likes how postgres handles things. What I would really prefer is that DataFusion always deals with UTC internally (like all internal math, expressions like now(), etc always use a UTC timestamp). I think this is what happens now If the input data doesn't specify a timezone, we should treat it like UTC (I know that is not what the arrow spec seems to say) If the user wants to see times / dates in their current locale's timezone, that can be handled by the end client (e.g. datafusion-cli) rather than forcing the entire processing chain to handle arbitrary timezones just for output display. -- 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]
