parthchandra commented on issue #468: URL: https://github.com/apache/datafusion-comet/issues/468#issuecomment-2137936443
IIRC there were differences in output between Spark 3.2 and Spark 3.4 for the timestamp_ntz type. Taking a closer look, the definition of timestamp_ntz (in Spark) essentially means that the value should be left untouched. So a value - `0` means `1970-01-01 00:00:00` in the session timezone. In the example above, the value is `-1` so the correct output for timezone_ntz (millis) should be `1960-12-31 23:59:59` (ignoring the millis). Spark 3.2's answer of `1970-01-01 05:29:59` seems incorrect to me. -- 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...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
