Skip to content

Commit aa90d4d

Browse files
committed
Warning added on patterns that require a refresh
1 parent 93697e0 commit aa90d4d

File tree

2 files changed

+10
-3
lines changed

2 files changed

+10
-3
lines changed

design-patterns/design-pattern-data-vault-hub.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,12 @@
11
# Design Pattern - Data Vault - Hub table
22

3+
---
4+
**NOTE**
5+
6+
This design pattern requires a major update to refresh the content.
7+
8+
---
9+
310
## Purpose
411

512
This Design Pattern describes how to load data into Data Vault Hub style tables. It is a specification of the Hub ETL process.
@@ -8,7 +15,7 @@ This Design Pattern describes how to load data into Data Vault Hub style tables.
815

916
Loading data into Hub tables is a relatively straightforward process with a clearly defined location in the architecture: it is applied when loading data from the Staging Layer to the Integration Layer.
1017

11-
The Hub is a vital component of a Data Vault solution, making sure that Data Warehouse keys are distributed properly and at the right point in time.
18+
The Hub is a vital component of a Data Vault solution, making sure that Data Warehouse keys are distributed properly and at the right point in time.
1219

1320
Decoupling key distribution and managing historical information (changes over time) is essential to reduce loading dependencies. It also simplifies (flexible) storage design in the Data Warehouse.
1421

@@ -52,7 +59,7 @@ To cater for a situation where multiple Load Date / Time stamp values exist for
5259

5360
## Considerations and Consequences
5461

55-
Multiple passes on the same Staging Layer data set are likely to be required: once for the Hub table(s) but also for any corresponding Link and Satellite tables.
62+
Multiple passes on the same Staging Layer data set are likely to be required: once for the Hub table(s) but also for any corresponding Link and Satellite tables.
5663

5764
Defining Hub ETL processes as atomic modules, as defined in this Design Pattern, means that many Staging Layer tables load data to the same central Hub table. All processes will be very similar with the only difference being the mapping between the Staging Layer business key attribute and the target Hub business key counterpart.
5865

design-patterns/design-pattern-data-vault-satellite.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
---
44
**NOTE**
55

6-
This design pattern requires a major update.
6+
This design pattern requires a major update to refresh the content.
77

88
---
99

0 commit comments

Comments
 (0)