The project already used Polars lazy frames end to end. I relied on its Arrow interop to register frames directly with the database engine without materialising intermediate files, and used it to build test fixtures and sample inputs. No changes to the existing transform code were needed.
- What worked
- Arrow-backed interchange with the database engine was zero-copy and preserved nullable integers, dates and timestamps correctly.