counterweight/data-dwh-dbt-project
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merged PR 2094: Removing lifecycle logic from int_core__accommodation

Browse source 
Removing lifecycle logic from int_core__accommodation
This logic is now available on int_core__mtd_accommodation_lifecycle

Related work items: #17312
This commit is contained in:
Oriol Roqué Paniagua 2024-06-21 14:13:42 +00:00
parent ef80637a9b
commit f23e210129
2 changed files with 5 additions and 229 deletions
Download patch file Download diff file Expand all files Collapse all files

141
models/intermediate/core/int_core__accommodation.sql
View file

@ -1,39 +1,7 @@
{{ config(materialized="table", unique_key="id_accommodation") }}
with
stg_core__booking as (select * from {{ ref("stg_core__booking") }}),
stg_core__accommodation as (select * from {{ ref("stg_core__accommodation") }}),
int_core__country as (select * from {{ ref("int_core__country") }}),
ranked_bookings as (
select
scb.id_accommodation,
scb.created_at_utc,
row_number() over (
partition by scb.id_accommodation order by scb.created_at_utc desc
) as reverse_booking_rank
from stg_core__booking scb
),
first_and_last_bookings as (
select
id_accommodation,
min(created_at_utc) as first_time_booked_at_utc,
max(created_at_utc) as last_time_booked_at_utc
from ranked_bookings
group by id_accommodation
),
accommodation_booking_main_dates as (
select
fb.id_accommodation,
fb.first_time_booked_at_utc,
fb.last_time_booked_at_utc,
rb.created_at_utc as second_to_last_time_booked_at_utc
from first_and_last_bookings fb
left join
ranked_bookings rb
on fb.id_accommodation = rb.id_accommodation
-- to select second to last booking, it's the 2nd apperance in descending creation time order
and rb.reverse_booking_rank = 2
),
accommodation_with_lifecycle_dates as (
int_core__country as (select * from {{ ref("int_core__country") }})
select
sca.id_accommodation,
sca.id_creating_user as id_user_host,
@ -58,111 +26,6 @@ select
date(sca.created_at_utc) as created_date_utc,
sca.updated_at_utc,
date(sca.updated_at_utc) as updated_date_utc,
abmd.first_time_booked_at_utc,
date(abmd.first_time_booked_at_utc) as first_time_booked_date_utc,
abmd.last_time_booked_at_utc,
date(abmd.last_time_booked_at_utc) as last_time_booked_date_utc,
abmd.second_to_last_time_booked_at_utc,
date(abmd.second_to_last_time_booked_at_utc) as second_to_last_time_booked_date_utc,
sca.dwh_extracted_at_utc,
-- adding updated_at to account for temporal variability of the status and booking-related dates
date_trunc('month', now()::date) as current_month,
case when abmd.first_time_booked_at_utc is not null then true else false end as accommodation_has_at_least_one_booking,
case when date_trunc('month', created_at_utc) = date_trunc('month', now()::date) then true else false end as accommodation_was_created_this_month,
case when date_trunc('month', first_time_booked_at_utc) = date_trunc('month', last_time_booked_at_utc) then true else false end as accommodation_has_first_booking,
case when date_trunc('month', last_time_booked_at_utc) = date_trunc('month', now()::date) then true else false end as has_been_booked_within_current_month,
case when date_trunc('month', last_time_booked_at_utc) + interval '6 months' > date_trunc('month', now()::date) then true else false end as has_been_booked_within_last_6_months,
case when date_trunc('month', last_time_booked_at_utc) + interval '12 months' > date_trunc('month', now()::date) then true else false end as has_been_booked_within_last_12_months,
case when date_trunc('month', last_time_booked_at_utc) + interval '12 months' = date_trunc('month', now()::date) then true else false end as last_booking_was_12_months_ago,
case when date_trunc('month', second_to_last_time_booked_at_utc) + interval '12 months' < date_trunc('month', last_time_booked_at_utc) then true else false end as had_previous_booking_more_than_12_months_before_the_last
sca.dwh_extracted_at_utc
from stg_core__accommodation sca
left join int_core__country icc on sca.id_country = icc.id_country
left join
accommodation_booking_main_dates abmd
on sca.id_accommodation = abmd.id_accommodation
)
select
id_accommodation,
id_user_host,
id_payment_validation_set,
friendly_name,
country_iso_2,
country_name,
country_preferred_currency_code,
is_active,
town,
postcode,
address_line_1,
address_line_2,
verification_level,
floor_area,
number_of_floors,
number_of_bedrooms,
number_of_bathrooms,
number_of_other_rooms,
construction_details,
case
-- 01-New: The listing has been created this month and has not had any booking
when
not accommodation_has_at_least_one_booking
and accommodation_was_created_this_month
then '01-New'
-- 02-Never Booked: The listing has been created before this month and has not had any booking
when
not accommodation_has_at_least_one_booking
and not accommodation_was_created_this_month
then '02-Never Booked'
-- 03-First Time Booked: The listing has been booked for the first time and it has been created this month
when
accommodation_has_first_booking
and has_been_booked_within_current_month
then '03-First Time Booked'
-- 04-Active: The listing has had at least 1 booking in its history and it's been less than 12 months since the last booking
-- and is not reactivated and is not FTB
when
accommodation_has_at_least_one_booking
and has_been_booked_within_last_12_months
-- not reactivated
and not (
had_previous_booking_more_than_12_months_before_the_last
and has_been_booked_within_current_month
)
-- not FTB
and not (
accommodation_has_first_booking
and has_been_booked_within_current_month
)
then '04-Active'
-- 05-Churning: The listing has been booked at least once and it's been 12 months since the last booking
when
accommodation_has_at_least_one_booking
and last_booking_was_12_months_ago
then '05-Churning'
-- 06-Inactive: The listing has been booked at least once and it's been more than 12 months since the last booking
when
accommodation_has_at_least_one_booking
and not has_been_booked_within_last_12_months
and not last_booking_was_12_months_ago
then '06-Inactive'
-- 07-Reactivated: The listing was churned/inactive but has had a new booking this month
when
had_previous_booking_more_than_12_months_before_the_last
and has_been_booked_within_current_month
then '07-Reactivated'
else Null
end as accommodation_lifecycle_state,
has_been_booked_within_current_month,
has_been_booked_within_last_6_months,
has_been_booked_within_last_12_months,
created_at_utc,
created_date_utc,
updated_at_utc,
updated_date_utc,
first_time_booked_at_utc,
first_time_booked_date_utc,
last_time_booked_at_utc,
last_time_booked_date_utc,
second_to_last_time_booked_at_utc,
second_to_last_time_booked_date_utc,
dwh_extracted_at_utc
from accommodation_with_lifecycle_dates

93
models/intermediate/core/schema.yaml
View file

@ -502,32 +502,7 @@ models:
It contains information regarding the host this accommodation is linked to,
the geographic details, the preferred currency according to the country, details about
the listing itself (floors, bedrooms, etc) and time-related information of when the
listing was created, booked for the first time, last time, and second-to-last time.
The information regarding the booking-related time allows for the current status of
any listing regarding its activity. There's no history, it's just the most up-to-date
status of the listing activity. This information is encapsulated in the following columns:
accommodation_lifecycle_state: contains one of the following states
- 01-New: Listings that have been created in the current month, without bookings
- 02-Never Booked: Listings that have been created before the current month, without bookings.
- 03-First Time Booked: Listings that have been booked for the first time in the current month.
- 04-Active: Listings that have booking activity in the past 12 months (that are not FTB nor reactivated)
- 05-Churning: Listings that are becoming inactive because of lack of bookings in the past 12 months
- 06-Inactive: Listings that have not had a booking for more than 12 months.
- 07-Reactivated: Listings that have had a booking in the current month that were inactive or churning before.
- Finally, if none of the logic applies, which should not happen, null will be set and a dbt alert will raise.
Since the states of Active, First Time Booked and Reactivated indicate certain booking activity and are
mutually exclusive, the model also provides information of the recency of the bookings by the following
booleans:
- has_been_booked_in_1_month: If a listing has had a booking created in the current month
- has_been_booked_in_6_months: If a listing has had a booking created in the past 6 months
- has_been_booked_within_last_12_months: If a listing has had a booking created in the past 12 months
Note that if a listing has had a booking created this month, all 3 columns will be true. Similarly,
if the last booking created to a listing was 5 months ago, only the column has_been_booked_in_1_month
will be false; while the other 2 will be true.
listing was created.
columns:
- name: id_accommodation
@ -569,7 +544,8 @@ models:
Boolean to indicate if the listing is active or not. If false, this is considered as a
hard deactivation - meaning no more bookings can be assigned to this listing. However,
even if a listing is active, that does not necessarily mean that it's receiving bookings.
Do not confuse this column with the lifecycle activity of a listing.
Do not confuse this column with the lifecycle activity of a listing that is computed in
int_core__mtd_accommodation_lifecycle.
- name: town
data_type: character varying
@ -604,27 +580,6 @@ models:
- name: construction_details
data_type: character varying
- name: accommodation_lifecycle_state
data_type: character varying
description: |
Contains the lifecycle state of a Listing. The accepted values are:
01-New, 02-Never Booked, 03-First Time Booked, 04-Active, 05-Churning, 06-Inactive,
07-Reactivated. Failing to implement the logic will result in alert.
tests:
- not_null
- name: has_been_booked_within_current_month
data_type: boolean
description: If the listing has had a booking created in the current month.
- name: has_been_booked_within_last_6_months
data_type: boolean
description: If the listing has had a booking created in the past 6 months.
- name: has_been_booked_within_last_12_months
data_type: boolean
description: If the listing has had a booking created in the past 12 months.
- name: created_at_utc
data_type: timestamp
description: Timestamp of when the listing was created. Cannot be null.
@ -643,48 +598,6 @@ models:
data_type: date
description: Date of when the listing was last updated according to the backend.
- name: first_time_booked_at_utc
data_type: timestamp
description: |
Timestamp of the first booking created for a given listing. Can be null if the listing
has never had a booking associated with it.
- name: first_time_booked_date_utc
data_type: date
description: |
Date of the first booking created for a given listing. Can be null if the listing
has never had a booking associated with it.
- name: last_time_booked_at_utc
data_type: timestamp
description: |
Timestamp of the last booking created for a given listing. Can be null if the listing
has never had a booking associated with it. Can be the same as first_time_booked_at_utc
if the listing only had 1 booking in its history.
- name: last_time_booked_date_utc
data_type: date
description: |
Date of the last booking created for a given listing. Can be null if the listing
has never had a booking associated with it. Can be the same as first_time_booked_date_utc
if the listing only had 1 booking in its history.
- name: second_to_last_time_booked_at_utc
data_type: timestamp
description: |
Timestamp of the second-to-last booking created for a given listing, meaning the creation
time of the booking that precedes the last one. It's relevant for the reactivation computation
on the lifecycle. Can be null if the listing has never had a booking associated with it or if
the listing only had 1 booking in its history.
- name: second_to_last_time_booked_date_utc
data_type: date
description: |
Date of the second-to-last booking created for a given listing, meaning the creation
date of the booking that precedes the last one. It's relevant for the reactivation computation
on the lifecycle. Can be null if the listing has never had a booking associated with it or if
the listing only had 1 booking in its history.
- name: dwh_extracted_at_utc
data_type: timestamp
description: Timestamp of when the accommodation record was extracted from the backend into the DWH.