runtime
55 / 88

task Deduplication · medium

Audit conflicting event retries

Report only retried event keys. Return event_key, the smallest id as canonical_id, the event_type from that canonical row as canonical_type, and the number of additional ingestion rows as retry_count.

what to return

Columns
event_keycanonical_idcanonical_typeretry_count in this order
Rows
2 rows · in the order asked
Watch for
Deduplicate globally by event_key, keeping the smallest id; a retry may have a conflicting payload.
Use (occurred_at, id) as the total event order; equal timestamps follow id order. All times are UTC.
Count all retry rows even when their payload differs. Order by event_key.
Skill
Separate logical event identity from ingestion row identity. Refresher: Sessionize an event stream →

expected result

Your query should return exactly these columns and values. Run it and compare.

expected result2 rows · in this order
event_keycanonical_idcanonical_typeretry_count
a33purchase1
i328purchase1

all 2 rows

data you can query

Sample rows from each table. Each column shows its type underneath; → marks a link to another table.

market_web_events7 columns · 38 rows
idinteger · keyevent_keytextshopper_idinteger → shoppersoccurred_attextevent_typetextchanneltextcart_idtext
1a112025-05-01 09:00:00viewemailA
2a212025-05-01 09:05:00checkoutdirectA
3a312025-05-01 09:10:00purchasedirectA
4a312025-05-01 09:10:00purchasedirectA
5b112025-05-01 10:00:00viewsearchB

showing 5 of 38 rows

solution.sql
 

Hints and the answer are always available. Using them counts the question as solved with help.