Thingies
This commit is contained in:
parent
2b6c385b8c
commit
7480222cc7
7 changed files with 49 additions and 13 deletions
|
|
@ -42,4 +42,9 @@ WHERE
|
|||
|
||||
Bear in mind that how to define the strategy to determine what should be loaded is up to the engineer. Any SQL can be placed within the `if is_incremental()` block. In the example above, we have a date field that easily signals what's the most recent date the table has currently seen.
|
||||
|
||||
##
|
||||
## Sources and seeds
|
||||
|
||||
Seeds are local files that you upload to a DWH from dbt. You place them as CSVs in the `seeds` folder.
|
||||
|
||||
|
||||
Sources are an abstraction layer on top of the input tables. They are not strictly necessary, but can help make the project more structured. To create sources, you create a `sources.yml` file and place it in the `models` dir.
|
||||
|
|
@ -105,12 +105,4 @@ dbt makes sense nowadays because the modern data stack makes transformations wit
|
|||
|
||||
- `dbt_project.yml`: header of the project, with stuff like versioning, the default profile for the project, the paths to different folders, etc.
|
||||
|
||||
This is a pic of the data flow we are going to build: 
|
||||
|
||||
## Sources and seeds
|
||||
|
||||
Seeds are local files that you upload to a DWH from dbt. You place them as CSVs in the `seeds` folder.
|
||||
|
||||
|
||||
Sources are an abstraction layer on top of the input tables.
|
||||
|
||||
This is a pic of the data flow we are going to build: 
|
||||
Loading…
Add table
Add a link
Reference in a new issue