Hubs are one of the core building blocks of a Data Vault. Hubs record a unique list of all business keys for a single entity. For example, a Hub may contain a list of all Customer IDs in the business.
Watch the video¶
Prefer a video? This video has a great overview of the content on this page.
In general, Hubs consist of 4 columns, described below.
Primary Key (src_pk)¶
A primary key (or surrogate key) which is usually a hashed representation of the natural key.
Natural Key / Business Key (src_nk)¶
This is usually a formal identification for the record, such as a customer ID or order number. Usually called the business key because this value has meaning in business processes such as transactions and events.
Load Date/Timestamp (src_ldts)¶
A load date or load date timestamp. This identifies when the record was first loaded into the database.
Record Source (src_source)¶
The source for the record. This can be a code which is assigned to a source name in an external lookup table,
or a string directly naming the source system.
1 from the staging section,
which is the code for
Creating Hub models¶
Create a new dbt model as before. We'll call this one
To create a Hub model, we simply copy and paste the above template into a model named after the Hub we are creating. AutomateDV will generate a Hub using parameters provided in the next steps.
The recommended materialisation for Hubs is
incremental, as we load and add new records to the existing data set.
Adding the metadata¶
Let's look at the metadata we need to provide to the hub macro.
We provide the column names which we would like to select from the staging area (
Using our knowledge of what columns we need in our
hub_customer Hub, we can identify columns in our
staging layer which map to them:
When we provide the metadata above, our model should look like the following:
1 2 3 4 5 6 7 8 9 10
See our metadata reference for more detail on how to provide metadata to Hubs.
With our metadata provided and our model complete, we can run dbt to create our
hub_customer Hub, as follows:
dbt run -s +hub_customer
The resulting Hub table will look like this:
Loading hubs from multiple sources¶
In some cases, we may need to load Hubs from multiple sources, instead of a single source as we have seen so far. This may be because we have multiple source staging tables, each of which contains a natural key for the Hub. This would require multiple feeds into one table: dbt prefers one feed, so we perform a union operation on the separate sources together and load them as one.
The data can and should be combined because these records have a truly identical key (same business meaning).
hub macro will perform a union operation to combine the tables using that key, and create a Hub containing
a complete record set.
The metadata needed to create a multi-source Hub is identical to a single-source Hub, we just provide a list of sources (usually multiple staging areas) rather than a single source, and the hub macro will handle the rest:
If your primary key and natural key columns have different names across the different
tables, they will need to be aliased to the same name in the respective staging layers
derived column configuration, using the stage macro in the staging layer.
1 2 3 4 5 6 7 8 9 10 11 12 13
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
See the Hub metadata reference for more examples.