The CRM export added a column that your contract does not allow. A plain read now returns four columns, and every downstream select gets an unexpected shape.
Contract: customer_id int, name string, email string.
Read paths['customers'] with an explicit schema for exactly those three fields, then return them sorted by customer_id ascending.
:::{note} An explicit schema ignores extra columns instead of failing. That is one of the safest ways to absorb additive drift - the file may grow, your contract does not. :::
| customer_id | name | |
|---|---|---|
| 1001 | Asha Rao | asha@example.com |
These files are loaded into this browser when you run. Their paths are handed to your code as the third argument: solve(spark, dfs, paths). Read one with spark.read.csv(paths['users'], header=True), or skip the read and use dfs['users'].
customers]Column names and order must match. Sort order is specified in the question.