Blue Heron Rides event report
The operations lead needs departure and arrival counts by route for the dispatch review. The bronze events feed contains a repeated departure and an unmatched trip reference; the trips table supplies valid keys and route names. Deliver raw and accepted pipeline tables, one row per business event, a quality audit and a route report. The audit must account separately for unmatched references and duplicate events.
Blue Heron Rides receives trip events from its dispatch system. Two feed rows describe the same departure, and another event points to a trip that does not exist. Operations needs route-level departure and arrival counts without either problem inflating the report.
Land the finite event snapshot, declare the trip-reference rule as an expectation and remove repeated business events. The event id identifies an ingestion row; trip_id, event_type and event_at identify the event the business wants to count. Keep a representative source id so you can trace that choice. Build the route summary only after those rules have been applied, then reconcile input, rejected and duplicate counts. This workspace processes a bounded snapshot. The outputs and dependency graph let you practice pipeline logic, but they do not establish a watermark policy or production streaming throughput.