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

change "tests:" to "data_tests:"

Browse source
This commit is contained in:
Pablo Martin 2025-01-13 16:00:35 +01:00
parent db1edf7a1c
commit c3c628aec4
29 changed files with 1565 additions and 1565 deletions
Download patch file Download diff file Expand all files Collapse all files

200
models/reporting/general/schema.yml
View file

@ -203,18 +203,18 @@ models:
description: A unique ID for the record, derived from concatenating the
currencies, date, source and version. Currency order is relevant
(EURUSD != USDEUR).
tests:
data_tests:
- not_null
- unique
- name: from_currency
data_type: character
description: The source currency, represented as an ISO 4217 code.
tests:
data_tests:
- not_null
- name: to_currency
data_type: character
description: The target currency, represented as an ISO 4217 code.
tests:
data_tests:
- not_null
- name: rate
data_type: numeric
@ -228,13 +228,13 @@ models:
always be one.
The rate can be smaller than one, but can't be negative.
tests:
data_tests:
- not_negative_or_zero
- not_null
- name: rate_date_utc
data_type: date
description: The date in which the rate record is relevant.
tests:
data_tests:
- not_null
- name: source
data_type: text
@ -249,7 +249,7 @@ models:
in nature) or `guess` (the rate sits in the past and is a guess in
nature). Note that one currency pair can have multiple rate versions
on the same date.
tests:
data_tests:
- accepted_values:
values:
- guess
@ -262,7 +262,7 @@ models:
For external sources, this will be the point in time when the
information was obtained from them. For stuff we make up here in the
DWH, this will be the point in time when we made the assumption.
tests:
data_tests:
- not_null
- name: simple_exchange_rates
@ -274,7 +274,7 @@ models:
The time granularity is daily. Each record holds a currency pair for a
specific day. You will only find one conversion rate per currency pair and
date.
tests:
data_tests:
- dbt_utils.unique_combination_of_columns:
combination_of_columns:
- from_currency
@ -284,22 +284,22 @@ models:
- name: from_currency
data_type: character
description: The source currency, represented as an ISO 4217 code.
tests:
data_tests:
- not_null
- name: to_currency
data_type: character
description: The source currency, represented as an ISO 4217 code.
tests:
data_tests:
- not_null
- name: rate
data_type: numeric
description: The target currency, represented as an ISO 4217 code.
tests:
data_tests:
- not_null
- name: rate_date_utc
data_type: date
description: The date in which the rate record is relevant.
tests:
data_tests:
- not_null
- name: updated_at_utc
data_type: timestamp with time zone
@ -307,7 +307,7 @@ models:
For external sources, this will be the point in time when the
information was obtained from them. For stuff we make up here in the
DWH, this will be the point in time when we made the assumption.
tests:
data_tests:
- not_null
- name: mtd_aggregated_metrics
@ -317,7 +317,7 @@ models:
It's the main source of information for the Main KPIs reporting, specifically
on the MTD (Month To Date) and the Monthly Overview.
tests:
data_tests:
- dbt_utils.unique_combination_of_columns:
combination_of_columns:
- date
@ -329,25 +329,25 @@ models:
- name: year
data_type: int
description: Year number of the given date.
tests:
data_tests:
- not_null
- name: month
data_type: int
description: Month number of the given date.
tests:
data_tests:
- not_null
- name: day
data_type: int
description: Day monthly number of the given date.
tests:
data_tests:
- not_null
- name: is_end_of_month
data_type: boolean
description: Is end of month, 1 for yes, 0 for no.
tests:
data_tests:
- not_null
- name: is_current_month
@ -355,7 +355,7 @@ models:
description: |
Checks if the date is within the current executed month,
1 for yes, 0 for no.
tests:
data_tests:
- not_null
- name: is_end_of_month_or_yesterday
@ -363,7 +363,7 @@ models:
description: |
Checks if the date is end of month or yesterday,
1 for yes, 0 for no.
tests:
data_tests:
- not_null
- name: first_day_month
@ -371,7 +371,7 @@ models:
description: |
First day of the month corresponding to the date field.
It comes from int_dates_mtd logic.
tests:
data_tests:
- not_null
- name: date
@ -379,7 +379,7 @@ models:
description: |
Main date for the computation, that is used for filters.
It comes from int_dates_mtd logic.
tests:
data_tests:
- not_null
- latest_date_is_yesterday
@ -391,13 +391,13 @@ models:
dimension_display; this is, the name of the dimension for
displaying purposes.
tests:
data_tests:
- not_null
- name: dimension_value
data_type: string
description: The value or segment available for the selected dimension.
tests:
data_tests:
- not_null
- name: previous_year_date
@ -410,7 +410,7 @@ models:
- name: metric
data_type: text
description: Name of the business metric.
tests:
data_tests:
- not_null
- name: order_by
@ -422,7 +422,7 @@ models:
- name: number_format
data_type: text
description: Allows for grouping and formatting for displaying purposes.
tests:
data_tests:
- accepted_values:
values:
[
@ -475,7 +475,7 @@ models:
enforces that a booking/guest journey/listing/etc has a host with a deal assigned, which is
not necessarily the case.
tests:
data_tests:
- dbt_utils.unique_combination_of_columns:
combination_of_columns:
- date
@ -485,20 +485,20 @@ models:
- name: date
data_type: date
description: The last day of the month for historic metrics.
tests:
data_tests:
- not_null
- name: id_deal
data_type: character varying
description: Id of the deal associated to the host.
tests:
data_tests:
- not_null
- name: main_deal_name
data_type: string
description: |
Main name for this ID deal.
tests:
data_tests:
- not_null
- name: main_billing_country_iso_3_per_deal
@ -510,19 +510,19 @@ models:
- name: year
data_type: int
description: year number of the given date.
tests:
data_tests:
- not_null
- name: month
data_type: int
description: month number of the given date.
tests:
data_tests:
- not_null
- name: day
data_type: int
description: day monthly number of the given date.
tests:
data_tests:
- not_null
- name: monthly_growth_score_by_deal
@ -562,7 +562,7 @@ models:
Lastly, this model provides informative date fields, deal attributes, absolute
metric values and MoM & YoY relative incrementals to enrich reporting.
tests:
data_tests:
- dbt_utils.unique_combination_of_columns:
combination_of_columns:
- date
@ -575,7 +575,7 @@ models:
Date corresponding to the last day of the month. Given month
metrics are inclusive to this date. Together with id_deal, it
acts as the primary key of this model.
tests:
data_tests:
- not_null
- name: id_deal
@ -583,21 +583,21 @@ models:
description: |
Unique identifier of a Deal. Together with date, it acts as
the primary key of this model.
tests:
data_tests:
- not_null
- name: main_deal_name
data_type: string
description: |
Main name for a Deal, representing the client.
tests:
data_tests:
- not_null
- name: has_active_pms
data_type: boolean
description: |
Does the deal have an active associated PMS.
tests:
data_tests:
- not_null
- name: active_pms_list
@ -646,7 +646,7 @@ models:
Informative field. It indicates the first day of the
month corresponding to date.
If date = 2024-09-30, this field will be 2024-09-01.
tests:
data_tests:
- not_null
- name: previous_1_month_first_day_month
@ -716,7 +716,7 @@ models:
for a specific deal. This value corresponds to
the given month. This value can be negative,
but not null.
tests:
data_tests:
- not_null
- name: previous_1_month_revenue_in_gbp
@ -767,7 +767,7 @@ models:
the previous month.
It can be null if any revenue used in the computation
is null or it's negative.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: -1
strictly: false
@ -781,7 +781,7 @@ models:
It can be null if any revenue used in the computation
is null or it's negative.
This field is used for the growth score computation.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: -1
strictly: false
@ -794,7 +794,7 @@ models:
months ago.
It can be null if any revenue used in the computation
is null or it's negative.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: -1
strictly: false
@ -808,7 +808,7 @@ models:
It can be null if any revenue used in the computation
is null or it's negative.
This field is used for the growth score computation.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: -1
strictly: false
@ -819,7 +819,7 @@ models:
Monthly value representing created bookings
for a specific deal. This value corresponds to
the given month. This value cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -833,7 +833,7 @@ models:
the previous month.
This value can be null, thus indicating that no
history is available.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -846,7 +846,7 @@ models:
monthly amount generated 12 months ago.
This value can be null, thus indicating that no
history is available.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -860,7 +860,7 @@ models:
It can be null if the bookings created in the
previous month are null.
This field is used for the growth score computation.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: -1
strictly: false
@ -874,7 +874,7 @@ models:
It can be null if the bookings created 12 months
ago are null.
This field is used for the growth score computation.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: -1
strictly: false
@ -885,7 +885,7 @@ models:
Monthly value representing the listings booked in month
for a specific deal. This value corresponds to
the given month. This value cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -899,7 +899,7 @@ models:
the previous month.
This value can be null, thus indicating that no
history is available.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -912,7 +912,7 @@ models:
monthly amount generated 12 months ago.
This value can be null, thus indicating that no
history is available.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -926,7 +926,7 @@ models:
It can be null if the listings booked in month in the
previous month are null.
This field is used for the growth score computation.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: -1
strictly: false
@ -940,7 +940,7 @@ models:
It can be null if the listings booked in month of 12
months ago are null.
This field is used for the growth score computation.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: -1
strictly: false
@ -954,7 +954,7 @@ models:
aggregated_revenue_to_first_day_month.
It can be negative if the sum is negative.
It cannot be null.
tests:
data_tests:
- not_null
- name: effective_deal_revenue_12_months_window
@ -968,7 +968,7 @@ models:
thus this value should not be reported.
It is used for the deal contribution share with respect
to the global revenue. It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -985,7 +985,7 @@ models:
thus this value should not be reported.
It is used for the deal contribution share with respect
to the global revenue. It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -997,7 +997,7 @@ models:
Represents the size of the deal in terms of revenue. In
other words, what's the percentage of the global revenue
that can be attributed to this deal. It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -1011,7 +1011,7 @@ models:
If more than one deal have the same share, the order is
not under control.
It cannot be null.
tests:
data_tests:
- not_null
- name: deal_created_bookings_12_months_window
@ -1022,7 +1022,7 @@ models:
aggregated_revenue_from_first_day_month to
aggregated_revenue_to_first_day_month.
It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -1037,7 +1037,7 @@ models:
aggregated_revenue_to_first_day_month.
It is used for the deal contribution share with respect
to the global created bookings. It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -1050,7 +1050,7 @@ models:
In other words, what's the percentage of the global created
bookings that can be attributed to this deal.
It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -1064,7 +1064,7 @@ models:
If more than one deal have the same share, the order is
not under control.
It cannot be null.
tests:
data_tests:
- not_null
- name: deal_avg_listings_booked_in_month_12_months_window
@ -1075,7 +1075,7 @@ models:
aggregated_revenue_from_first_day_month to
aggregated_revenue_to_first_day_month.
It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -1091,7 +1091,7 @@ models:
It is used for the deal contribution share with respect
to the global average listings booked in month.
It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -1105,7 +1105,7 @@ models:
In other words, what's the percentage of the global average listings
booked in month that can be attributed to this deal.
It cannot be null.
tests:
data_tests:
- not_null
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
@ -1119,7 +1119,7 @@ models:
If more than one deal have the same share, the order is
not under control.
It cannot be null.
tests:
data_tests:
- not_null
- name: avg_mom_growth_score
@ -1130,7 +1130,7 @@ models:
MoM shifted by one month of revenue.
It indicates the tendency of growth of the deal without
taking into account its revenue size. It cannot be null.
tests:
data_tests:
- not_null
- name: avg_yoy_growth_score
@ -1141,7 +1141,7 @@ models:
YoY shifted by one month of revenue.
It indicates the tendency of growth of the deal without
taking into account its revenue size. It cannot be null.
tests:
data_tests:
- not_null
- name: avg_growth_score
@ -1152,7 +1152,7 @@ models:
YoY and MoM shifted by one month of revenue.
It indicates the tendency of growth of the deal without
taking into account its revenue size. It cannot be null.
tests:
data_tests:
- not_null
- name: weighted_avg_growth_score
@ -1164,7 +1164,7 @@ models:
It's the main indicator towards measuring both growth
(if positive) or decay (if negative) while weighting
the financial impact this deal tendency can have.
tests:
data_tests:
- not_null
- name: categorisation_weighted_avg_growth_score
@ -1175,7 +1175,7 @@ models:
losers, flat, winners and top winners.
Currently the categorisation is based on the score itself
rather than selecting a top up/down.
tests:
data_tests:
- not_null
- accepted_values:
values:
@ -1202,7 +1202,7 @@ models:
description: |
The identifier of the booking. Acts as Primary Key to this table.
Cannot be null.
tests:
data_tests:
- not_null
- unique
@ -1210,7 +1210,7 @@ models:
data_type: string
description: |
Unique identifier of the account. It cannot be null.
tests:
data_tests:
- not_null
- name: main_billing_country
@ -1228,7 +1228,7 @@ models:
This field should be modified at the moment we have
a proper way to retrieve a common account name per deal.
It can contain duplicates.
tests:
data_tests:
- not_null
- name: hubspot_deal_name
@ -1246,7 +1246,7 @@ models:
data_type: string
description: |
The current status of the booking. Cannot be null.
tests:
data_tests:
- not_null
- name: program_name
@ -1254,7 +1254,7 @@ models:
description: |
The name of the program, or product bundle, applied to the booking.
Cannot be null.
tests:
data_tests:
- not_null
- name: booking_created_date_utc
@ -1262,7 +1262,7 @@ models:
description: |
Date of when the Booking record was created in the Backend.
Cannot be null.
tests:
data_tests:
- not_null
- name: booking_check_in_date_utc
@ -1270,14 +1270,14 @@ models:
description: |
Date of the Check-in of the Booking.
Cannot be null.
tests:
data_tests:
- not_null
- name: booking_check_out_date_utc
data_type: date
description: |
Date of the Check-out of the Booking.
tests:
data_tests:
- not_null
- name: booking_number_of_nights
@ -1296,7 +1296,7 @@ models:
description: |
Specifies the New Dash Version in which these users were
moved or joined.
tests:
data_tests:
- not_null
- name: user_in_new_dash_since_date_utc
@ -1350,7 +1350,7 @@ models:
not necessarily mean that it won't be in the future. Similarly, if
the booking is chargeable it does not necessarily mean that is actually
charged. It cannot be null.
tests:
data_tests:
- not_null
- name: is_booking_cancelled
@ -1389,7 +1389,7 @@ models:
additional metrics.
The data is segmented by deal and time window for detailed analysis.
tests:
data_tests:
- dbt_utils.unique_combination_of_columns:
combination_of_columns:
- date
@ -1402,20 +1402,20 @@ models:
description: |
The last day of the month or yesterday for historic metrics.
It's the same date as for KPIs related models.
tests:
data_tests:
- not_null
- name: id_deal
data_type: character varying
description: Id of the deal associated to the host.
tests:
data_tests:
- not_null
- name: time_window
data_type: character varying
description: |
Identifier of the time window used for the aggregation of the metrics.
tests:
data_tests:
- not_null
- accepted_values:
values:
@ -1445,14 +1445,14 @@ models:
data_type: string
description: |
Main name for this ID deal.
tests:
data_tests:
- not_null
- name: has_active_pms
data_type: boolean
description: |
Does the deal have an active associated PMS.
tests:
data_tests:
- not_null
- name: active_pms_list
@ -1503,7 +1503,7 @@ models:
Total amount of bookings created by the deal
in the time window. It can be null if no bookings
were created.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -1514,7 +1514,7 @@ models:
Average amount of listings booked in month by the deal
in the time window. It can be null if no listings
were booked.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -1555,7 +1555,7 @@ models:
Total amount of payments in GBP made by the guest
in the time window. It can be null if no payments
were made by the guest. It can be negative.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -1574,7 +1574,7 @@ models:
Total amount of resolution payments made to the host
in the time window. It can be null if no resolution
payments were made by the host.
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -1609,7 +1609,7 @@ models:
- name: id_verification
data_type: text
description: "unique Superhog generated id for this verification"
tests:
data_tests:
- unique
- not_null
@ -1622,7 +1622,7 @@ models:
- name: id_user_partner
data_type: text
description: "unique Superhog generated id for partner"
tests:
data_tests:
- not_null
- name: id_accommodation
@ -1632,7 +1632,7 @@ models:
- name: version
data_type: text
description: "value to identify if it is Guesty (V1) or E-deposit (V2)"
tests:
data_tests:
- accepted_values:
values:
- V1
@ -1641,7 +1641,7 @@ models:
- name: verification_source
data_type: text
description: "source of the verification for the booking"
tests:
data_tests:
- accepted_values:
values:
- Guesty
@ -1816,7 +1816,7 @@ models:
- name: id_deal
data_type: character varying
description: "Unique ID for this deal."
tests:
data_tests:
- unique
- not_null
@ -1829,7 +1829,7 @@ models:
description: "Count of distinct names the deal has in Core.
It might be the case that a deal has ony NULL value for a name,
so the count will be 0"
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -1843,7 +1843,7 @@ models:
description: "Count of distinct names the deal has in Hubspot.
It might be the case that a deal has ony NULL value for a name,
so the count will be 0"
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false
@ -1857,7 +1857,7 @@ models:
description: "Count of distinct names the deal has in Xero.
It might be the case that a deal has ony NULL value for a name,
so the count will be 0"
tests:
data_tests:
- dbt_expectations.expect_column_values_to_be_between:
min_value: 0
strictly: false