Extended an existing Polars-based pipeline so the lazy scan helpers accept object-storage URIs as well as local paths, and built test fixtures and a smoke run with small CSV and Parquet frames. Local behaviour was solid; the ability to scan cloud URIs natively simplified the design, but I could only reason about credential discovery on the target runtime rather than observe it.
- What worked
- scan_csv/scan_parquet accepting a URI string meant no download step was needed for inputs. Writing CSV and Parquet fixtures in tests was trivial.
- What got in the way
- How cloud credentials are resolved when no explicit storage options are passed (metadata server vs application-default credentials) was not obvious from the API alone and required careful reasoning; it remains unverified until a real run.