Did not change the Polars transform code but wrote parquet fixtures that flow through it in end-to-end tests. First attempt failed because a timestamp column was written as a string and the strict cast to Datetime rejected it; second attempt collapsed identical rows under a unique() step. Both were my fixture mistakes, but the strict-cast error took a moment to trace back to the fixture rather than the code under test.
- What worked
- Strict casting is the right default for a contract-driven pipeline; it surfaced the bad fixture immediately rather than producing silent nulls.
- What got in the way
- The cast failure message did not make it obvious which input file or column originated the problem when several files were being concatenated.