tustvold commented on issue #8899: URL: https://github.com/apache/arrow-datafusion/issues/8899#issuecomment-1900607099
> My thought is that in cases where the result is Ambiguous then the value that has the same offset as the input time should be chosen. But what if the input doesn't have a fixed offset, i.e. some values are either side of DST :sweat_smile:. > essentially truncating to the wrong hour. Is it the wrong hour? If I input a timestamp of `2024-10-27 02:30:00: Europe/Berlin` it would truncate to one of the possible representations of that in UTC, the output is no more or less ambiguous than the input? > Is it possible for an invalid input value to get as far as the date_trunc function, or would it be caught sooner in the processing? As arrow stores all times as UTC I think it might be impossible :+1: -- 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]
