SQLEasyofficialBenchmark eligiblefree
Incorrect customer join
Orders were remapped to customer_uuid. A finance report still joins customers.email and fans out on collisions. Restore the intended order-to-customer map using the mapping table.
| Field | Detail |
|---|---|
| Creator | PipelineArena · expert |
| Version | 2.0.0 |
| Time | 30 min |
| Credits | 2 |
| Completion | 0% · 0.0 rating |
| Hidden tests | 4 |
Objective
The report has one row per order, joined on the surrogate key, with unmatched orders listed.
| # | Success condition |
|---|---|
| 1 | No fan-out: report row count equals distinct order_id |
| 2 | Join uses customer_uuid / mapping table, not email |
| 3 | Orphan orders appear in unmatched_orders |
| 4 | Checksum of (order_id, customer_uuid) matches the hidden map |
| # | Visible instruction |
|---|---|
| 1 | Compare report row counts to orders. |
| 2 | Use customer_key_map from the migration. |
| 3 | Leave unmatched_orders for operations — do not drop them. |
Hidden tests score the final tables or files, not the exact syntax you used. Test implementation is never shown to participants.
Signed-in workspace: Open in app