The GitHub Actions job "Benchmarks" on texera.git/fix/8595-timestamp-cast-range has succeeded. Run started by GitHub user kz930 (triggered by kz930).
Head commit for run: c074933878adc8d88c0abd0b060b594fc44f5b6e / kary zheng <[email protected]> fix(operator): read a timestamp that states an offset The cast stopped on one. A reading that carries a zone cannot be converted to a column that holds none, so `2024-03-05T14:09:07Z` ended the cast where the previous generator had read it, and an explicit offset did the same. The engine reads the offset and keeps no zone for it: DateParserUtils parses the reading and java.sql.Timestamp holds the wall clock of the machine's own zone, so `...T14:09:07Z` is 06:09:07 where the machine is eight hours behind UTC. The helper now does that, which is also what the epoch-milliseconds branch beside it already did. The two spellings join the cases the timestamp test compares against parseField cell by cell, so what they should read is taken from the engine rather than written down and the pair says the same thing in any zone. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/35409960374 With regards, GitHub Actions via GitBox
