Addressed comments
This commit is contained in:
parent
eec21fe5da
commit
88083fc846
3 changed files with 12 additions and 5 deletions
|
|
@ -5829,7 +5829,8 @@ models:
|
|||
|
||||
The unique key corresponds to the deepest granularity of the model,
|
||||
in this case:
|
||||
- date_day,
|
||||
- date_day,
|
||||
- py_date_day,
|
||||
- id_deal,
|
||||
- has_id_check.
|
||||
|
||||
|
|
@ -5837,6 +5838,7 @@ models:
|
|||
- dbt_utils.unique_combination_of_columns:
|
||||
combination_of_columns:
|
||||
- date_day
|
||||
- py_date_day
|
||||
- has_payment
|
||||
- has_id_check
|
||||
columns:
|
||||
|
|
@ -5846,6 +5848,12 @@ models:
|
|||
tests:
|
||||
- not_null
|
||||
|
||||
- name: py_date_day
|
||||
data_type: date
|
||||
description: |
|
||||
Date on the previous year of when Guest Journeys have been completed.
|
||||
Note that this date can be NULL for leap days (29th February)
|
||||
|
||||
- name: has_payment
|
||||
data_type: string
|
||||
description: Has there been any guest payments on the guest journey.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue