-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdbt_project.yml
56 lines (48 loc) · 1.63 KB
/
dbt_project.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
name: 'stargazers'
version: '1.0'
config-version: 2
# This setting configures which "profile" dbt uses for this project. Profiles contain
# database connection information, and should be configured in the ~/.dbt/profiles.yml file
profile: 'stargazers'
# These configurations specify where dbt should look for different types of files.
# The `source-paths` config, for example, states that source models can be found
docs-paths: ["docs"]
analysis-paths: ["analysis"]
test-paths: ["tests"]
seed-paths: ["seed"]
macro-paths: ["macros"]
target-path: "target" # directory which will store compiled SQL files
log-path: "logs" # directory which will store DBT logs
clean-targets: # directories to be removed by `dbt clean`
- "target"
- "logs"
quoting:
database: true
schema: true
identifier: true
dispatch:
- macro_namespace: dbt_utils
search_order: ['airbyte_warehouse', 'dbt_utils']
vars:
'dbt_date:time_zone': 'America/Los_Angeles'
get_max_dt_lookback_window: 4 # Set how many days to look back when computing max dt for incremental
# Using these configurations, you can enable or disable models, change how they
# are materialized, and more!
models:
stargazers:
+dagster_freshness_policy:
maximum_lag_minutes: 540
cron_schedule: "0 9 * * *"
# When schema changes on models we are building, we should run dbt with --full-refresh flag explicitely
+on_schema_change: "fail"
+materialized: table
staging:
+tags: staging
+materialized: view
+schema: staging
core:
+materialized: view
+schema: core
mart:
+materialized: table
+schema: mart