-
Notifications
You must be signed in to change notification settings - Fork 3
/
dbt_project.yml
43 lines (33 loc) · 1.46 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
# Name your project! Project names should contain only lowercase characters
# and underscores. A good package name should reflect your organization's
# name or the intended use of these models
name: 'dbt_ml_example'
version: '1.0.0'
config-version: 2
# This setting configures which "profile" dbt uses for this project.
profile: dbt_bqml_example
# These configurations specify where dbt should look for different types of files.
# The `source-paths` config, for example, states that models in this project can be
# found in the "models/" directory. You probably won't need to change these!
source-paths: ["models"]
analysis-paths: ["analysis"]
test-paths: ["tests"]
data-paths: ["data"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]
target-path: "target" # directory which will store compiled SQL files
clean-targets: # directories to be removed by `dbt clean`
- "target"
- "dbt_modules"
on-run-start:
# Create the ml_model_audit DATASET at the start of the dbt run, if it doesn't exist
- '{% do adapter.create_schema(api.Relation.create(target.project, "ml_model_audit")) %}'
# Create the ml_model_audit TABLE at the start of the dbt run, if it doesn't exist
- "{{ dbt_ml.create_model_audit_table() }}"
models:
dbt_ml_example:
# Applies to all files under models/example/ unless overriden in sql file
materialized: view
vars:
"dbt_ml:audit_schema": "ml_model_audit"
"dbt_ml:audit_table": "ml_models"