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: ca67ce12b759b0b7093fc499c5839e9c88c149a1 / kary zheng <[email protected]> fix(operator): keep the resolution a timestamp column arrived in The cast narrowed one. A column the engine already holds as a moment went through the same astype as freshly parsed text, so 14:09:07.123456789 and 14:09:07.123456001 both came back as .123456 and two rows the run tells apart became one. The previous generator left such a column alone. parseField hands a java.sql.Timestamp back untouched and that class counts nanoseconds, so there is nothing for this branch to decide: the column is returned at the resolution it arrived in, zoned or not. The text branch below is unchanged and still reads into microseconds, which is what the years past the nanosecond edge need. A test casts a timestamp column to timestamp and compares the two values cell by cell against parseField, which is how the rest of the spec compares a cast. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/35575644911 With regards, GitHub Actions via GitBox
