Snapshot configurations
Related documentation
Available configurations
Snapshot-specific configurations
- YAML
- Config block
snapshots:
General configurations
- YAML
- Config block
Configuring snapshots
Snapshots can be configured in one of two ways:
- Using a
config
block within a snapshot, or - From the
dbt_project.yml
file, under thesnapshots:
key. To apply a configuration to a snapshot, or directory of snapshots, define the resource path as nested dictionary keys.
Snapshot configurations, like model configurations, are applied hierarchically — configurations applied to a marketing
subdirectory will take precedence over configurations applied to the entire jaffle_shop
project.
Examples
target_schema
configuration to all snapshots
Apply the To apply a configuration to all snapshots, including those in any installed packages, nest the configuration directly under the snapshots
key:
snapshots:+target_schema: snapshots
target_schema
configuration to all snapshots in your project
Apply the To apply a configuration to all snapshots in your project only (i.e. excluding any snapshots in installed packages), provide your project name as part of the resource path.
For a project named jaffle_shop
:
snapshots:jaffle_shop:+target_schema: snapshot_data
Similarly, you can use the name of an installed package to configure snapshots in that package.
Apply configurations to one snapshot only
We recommend using config
blocks if you need to apply a configuration to one snapshot only.
{% snapshot orders_snapshot %}{{config(unique_key='id',strategy='timestamp',updated_at='updated_at')}}-- Pro-Tip: Use sources in snapshots!select * from {{ source('jaffle_shop', 'orders') }}{% endsnapshot %}
You can also use the full resource path (including the project name, and subdirectories) to configure an individual snapshot from your dbt_project.yml
file.
For a project named jaffle_shop
, with a snapshot file within the snapshots/postgres_app/
directory, where the snapshot is named orders_snapshot
(as above), this would look like:
snapshots:jaffle_shop:postgres_app:orders_snapshot:+unique_key: id+strategy: timestamp+updated_at: updated_at