Loadingone moment…
Sign in to run and submit your work
Reading is open to everyone. Running code and saving drafts need an account so your work is yours and comes back on your next visit.
or
CODE WORKSPACE
Return query_id, query_label, gb_scanned, partitions_scanned, and triage_status.
Result columns · in this order
query_idquery_labelgb_scannedpartitions_scannedtriage_statusHow to approach it
Read bytes scanned and partitions touched before discussing optimization.
Sample input
| query_id | query_label | gb_scanned | partitions_scanned |
|---|---|---|---|
| 2 | orders_export | 240 | 8 |
| 6 | adhoc_select_star | 180 | 8 |
| 4 | event_funnel | 85 | 6 |
3 rows — all rows shown.
Expected output
| query_id | triage_status |
|---|---|
| 2 | full_scan_review |
| 6 | full_scan_review |
| 4 | expensive_review |
3 rows — all rows shown.
Constraints
Use full_scan_review when gb_scanned >= 100 and partitions_scanned >= 8, expensive_review when gb_scanned >= 50, otherwise acceptable. Order by gb_scanned DESC, query_id.
Expected skills
Warehouse cost reasoning from query-history metadata.
Submit for review to find out what your query gets right, what it gets wrong, and how it compares with the best working query for this exercise.
This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.