-
Notifications
You must be signed in to change notification settings - Fork 11
Point In Time
Hoa Le edited this page May 23, 2023
·
1 revision
This table is all about defining the pit tables that show the historical connection between satellite entries in your Data Vault. Here you configure the names of the pits, the names of the columns and where to find them within the source.
The following columns are required in the table/worksheet called "pit" inside your metadata:
| Name | Explanation |
|---|---|
| Pit_Identifier | A globally unique identifier of a pit. |
| Pit_Physical_Table_Name | The name of this pit object. Will be used for naming the generated pit model. |
| Tracked_Entity | The globally unique identifier of the tracked hub or link the satellites are attached to. |
| Satellite_Identifiers | The globally unique identifier of the tracked satellites. Separated by a ; |
| Snapshot_Model_Name(optional) | The name of the snapshot relation. It needs to be available as a model inside this dbt project. |
| Snapshot_Trigger_Column(optional) | The name of the column inside the previously mentioned snapshot relation, that is boolean and identifies the snapshots that should be included in the PIT table. |
| Dimension_Key_Name(optional) | The desired name of the dimension key inside the PIT table. Should follow some naming conventions. Recommended is the name of the hashkey with a '_d' suffix. |
| Group_Name(optional) | Defines to which business object group this entry belongs, used for the folder structure of the dbt models as well as the visualization of the entities. |
See the following example values for each column. In total, they describe the satellite "solution_data_sfdc_lrn_s" from the parent hub "solution_h".
| Pit_Identifier | Pit_Physical_Table_Name | Tracked_Entity | Satellite_Identifiers | Snapshot_Model_Name | Snapshot_Trigger_Column | Dimension_Key_Name | Group_Name |
| P0001 | solution_sfdc_bp | H0006 | S0001;S0002 | Solution |
Table of Content