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

Adding protection names

Browse source
This commit is contained in:
uri 2024-10-07 17:18:41 +02:00
parent c503d797b6
commit 9424a96707
1 changed files with 34 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

59
models/intermediate/core/int_core__user_product_bundle.sql
View file

@ -1,18 +1,22 @@
{{ config(materialized="table", unique_key="id_user_product_bundle") }} {{ config(materialized="table", unique_key="id_user_product_bundle") }}
with with
stg_core__user_product_bundle as (select * from {{ ref("stg_core__user_product_bundle") }}), stg_core__user_product_bundle as (
int_core__user_host as (select * from {{ ref("int_core__user_host") }} select * from {{ ref("stg_core__user_product_bundle") }}
) ),
stg_core__protection_plan as (select * from {{ ref("stg_core__protection_plan") }}),
int_core__user_host as (select * from {{ ref("int_core__user_host") }})
select select
upb.id_user_product_bundle, upb.id_user_product_bundle,
upb.id_user as id_user_host, upb.id_user as id_user_host,
upb.id_product_bundle, upb.id_product_bundle,
upb.id_protection_plan, upb.id_protection_plan,
upb.product_bundle_name, upb.product_bundle_name,
upb.product_bundle_display_name, upb.product_bundle_display_name,
upb.display_on_front_end, pp.protection_name,
upb.chosen_product_services, pp.protection_display_name,
upb.display_on_front_end,
upb.chosen_product_services,
upb.starts_at_utc as original_starts_at_utc, upb.starts_at_utc as original_starts_at_utc,
upb.ends_at_utc as original_ends_at_utc, upb.ends_at_utc as original_ends_at_utc,
/* /*
@ -22,18 +26,21 @@ select
the effective fields (start_date and end_date) rather than the the effective fields (start_date and end_date) rather than the
backend ones (named as original_starts_at and original_ends_at). backend ones (named as original_starts_at and original_ends_at).
*/ */
greatest(date(upb.starts_at_utc), uh.lower_limit_migration_date_utc) as effective_start_date_utc, greatest(
case date(upb.starts_at_utc), uh.lower_limit_migration_date_utc
when upb.has_no_end_date then null ) as effective_start_date_utc,
else greatest(date(upb.ends_at_utc), uh.lower_limit_migration_date_utc) case
when upb.has_no_end_date
then null
else greatest(date(upb.ends_at_utc), uh.lower_limit_migration_date_utc)
end as effective_end_date_utc, end as effective_end_date_utc,
upb.has_no_end_date, upb.has_no_end_date,
upb.created_at_utc, upb.created_at_utc,
upb.created_date_utc, upb.created_date_utc,
upb.updated_at_utc, upb.updated_at_utc,
upb.updated_date_utc, upb.updated_date_utc,
upb.dwh_extracted_at upb.dwh_extracted_at
from stg_core__user_product_bundle upb from stg_core__user_product_bundle upb
/* /*
There are many not migrated users that have product bundles. There are many not migrated users that have product bundles.
Since users are not migrated, these bundles cannot be active. Since users are not migrated, these bundles cannot be active.
@ -41,6 +48,8 @@ In order to avoid potential upstream problems, it is enforced
that product bundles need to be from users that have been that product bundles need to be from users that have been
already migrated. already migrated.
*/ */
inner join int_core__user_host uh inner join
on upb.id_user = uh.id_user_host int_core__user_host uh
and uh.is_user_migrated = True on upb.id_user = uh.id_user_host
and uh.is_user_migrated = true
left join stg_core__protection_plan pp on upb.id_protection_plan = pp.id_protection_plan