SQLMediumofficialBenchmark eligiblefree
Vendor catalog merge
Three vendor extracts collide on sku. Apply source priority from scoring.yaml. Keep losers for audit. This is a multi-source merge, not the email natural-key collapse.
| Field | Detail |
|---|---|
| Creator | PipelineArena |
| Version | 2.0.0 |
| Time | 40 min |
| Scored checks | 16 |
Objective
products_master unique on sku with documented survivor attributes; products_losers retained.
| # | Success condition |
|---|---|
| 1 | One row per sku |
| 2 | Title and price from the highest-priority vendor that has them |
| 3 | Losers table has every discarded vendor row |
| 4 | Re-run does not duplicate master or losers |
| # | Visible instruction |
|---|---|
| 1 | Read vendor priority in scoring.yaml. |
| 2 | Collapse on sku; fill attributes by rank. |
| 3 | Write an audit table of non-survivors. |
Scoring checks the leftover tables or files, replay safety, and seeded variations — not the exact syntax you used. Check implementation is never shown to participants.
Signed-in workspace: Open in app