771b226888
Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310 |
||
|---|---|---|
| .. | ||
| int_core__booking_charge_events.sql | ||
| int_core__bookings.sql | ||
| int_core__check_in_cover_prices.sql | ||
| int_core__deal_id_master_list.sql | ||
| int_core__duplicate_bookings.sql | ||
| int_core__mtd_aggregated_metrics.sql | ||
| int_core__mtd_booking_metrics.sql | ||
| int_core__mtd_guest_journey_metrics.sql | ||
| int_core__price_plans.sql | ||
| int_core__unified_user.sql | ||
| int_core__verification_payments.sql | ||
| int_core__verification_request_completed_date.sql | ||
| int_core__verification_request_completeness.sql | ||
| int_core__verification_requests.sql | ||
| int_core__vr_check_in_cover.sql | ||
| schema.yaml | ||