Compared to a regular satellite, a reference Satellite does not hold a Hashkey of the parent Hub, since the parent reference Hub does not have a Hub Hashkey. Instead, all reference keys of the parent reference Hub are loaded in the reference Satellite to allow unique connections between them.

Besides that, a reference Satellite v0 shares the same features as a regular Satellite v0, which are:

Can handle multiple updates per batch, without losing intermediate changes. Therefore initial loading is supported.
Using a dynamic high-water-mark to optimize loading performance of multiple loads

Required Parameters

Parameters	Data Type	Required	Default Value	Explanation
parent_ref_keys	string/list	mandatory	–	Name of the references key(s) inside the parent reference Hub.
src_hashdiff	string	mandatory	–	Name of the hashdiff column of this satellite, that was created inside the staging area and is calculated out of the entire payload of this satellite. The stage must hold one hashdiff per satellite entity.
src_payload	list of strings	mandatory	–	A list of all the descriptive attributes that should be included in this satellite. Needs to be the columns that are feeded into the hashdiff calculation of this satellite.
source_model	string	mandatory	–	Name of the underlying staging model, must be available inside dbt as a model.

Optional Parameters

Parameters	Data Type	Required	Default Value	Explanation
src_ldts	string	optional	datavault4dbt. ldts_alias	Name of the ldts column inside the source model. Needs to use the same column name as defined as alias inside the staging model.
src_rsrc	string	optional	datavault4dbt. rsrc_alias	Name of the rsrc column inside the source model. Is optional, will use the global variable ‘datavault4dbt.rsrc_alias’. Needs to use the same column name as defined as alias inside the staging model.

Example 1

{{ config(materialized='incremental',
        schema='Core') }}

{%- set yaml_metadata -%}
source_model: stg_nation
parent_ref_keys: N_NATIONKEY
src_hashdiff: hd_nation_rs
src_payload:
    - N_COMMENT
    - N_NAME
    - N_REGIONKEY
{%- endset -%}      

{% set metadata_dict = fromyaml(yaml_metadata) %}

{{ datavault4dbt.ref_sat_v0(source_model=metadata_dict.get(source_model'),
                    parent_ref_keys=metadata_dict.get('parent_ref_keys'),
                    src_hashdiff=metadata_dict.get('src_hashdiff'),
                    src_payload=metadata_dict.get('src_payload')) }}

Description

parent_ref_keys:
- N_NATIONKEY: This reference Satellite would be attached to the reference Hub “Nation_rh” and therefore it must hold all the reference Keys of that Hub. In this case it would only be the column “N_NATIONKEY”
src_hashdiff:
- hd_nation_rs Since we recommend naming the hashdiff column similar to the name of the satellite entity, just with a prefix, this would be the hashdiff column of the reference satellite for Nation.
src_payload: This satellite would hold the columns ‘N_COMMENT’, ‘N_NAME’ and ‘N_REGIONKEY’, coming out of the underlying staging area. Must fit the input definition for the specified hashdiff column.
source_models:
- stg_nation: This satellite is loaded out of the stage for nation.

Compiled SQL

Click Me!

WITH


source_data AS (

    SELECT
        
        N_NATIONKEY,
        
        hd_nation_rs as hd_nation_rs,
        
        rsrc,
        ldts,
        N_COMMENT,
        N_NAME,
        N_REGIONKEY
    FROM datavault4dbt_demo.core_Stages.stg_nation
),




deduplicated_numbered_source AS (

    SELECT
    
    N_NATIONKEY,
    
    hd_nation_rs,
    
        rsrc,
        ldts,
        N_COMMENT,
        N_NAME,
        N_REGIONKEY
    
    FROM source_data
    QUALIFY
        CASE
            WHEN hd_nation_rs = LAG(hd_nation_rs) OVER(PARTITION BY N_NATIONKEY ORDER BY ldts) THEN FALSE
            ELSE TRUE
        END
),


records_to_insert AS (

    SELECT
    
    N_NATIONKEY,
    
    hd_nation_rs,
    
        rsrc,
        ldts,
        N_COMMENT,
        N_NAME,
        N_REGIONKEY
    FROM deduplicated_numbered_source

    )

SELECT * FROM records_to_insert