[daggy-u] [dbt] - Lesson 4, fetch your run artifacts #19968
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite. Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
tacastillo
force-pushed
the
erin/dev-58-dbt-lesson-4
branch
from
d854863 to
69ee496
Compare
tacastillo
force-pushed
the
02-21-_du-dbt_fetch_your_run_artifacts
branch
from
41c1df3 to
b8ec5c7
Compare
|
Deploy preview for dagster-university ready! ✅ Preview Built with commit a1ff875. |
erinkcochran87
changed the title
| @@ -0,0 +1,53 @@ | |||
| --- | |||
| title: 'Lesson 4: Customizing your execution' | |||
There was a problem hiding this comment.
Should we make this title specific, like "Customizing dbt's execution"?
There was a problem hiding this comment.
Hmm, I get what you're saying and I think this could be worded better, but to nit pick it to the utmost extent, we aren't customizing how dbt runs, but rather what happens within Dagster after dbt runs. wdyt?
| context.log.debug(result["compiled_code"]) | ||
| ``` | ||
|
|
||
| Once you've made these changes, restart your code location and run any of your dbt models. You should see the compiled SQL code for each model in the logs. |
There was a problem hiding this comment.
restart your code location
Specifically, kill dagster dev and then re-run, correct?
There was a problem hiding this comment.
That's one of the ways! The preferred ways would be either pressing the Reload Definitions button or pressing Option+Shift+R
Summary & Motivation
Making this a separate PR that folds into the larger LEsson 4 PR so I don't ruin your great writing with my dirty cruft.
How I Tested These Changes