Noam Finkelstein01/26/2023, 12:28 AM
Olivier Dupuis01/26/2023, 6:29 PM
becomes stale, it will run only
and whatever other upstream assets that need to be refreshed. • Whereas if my
becomes stale, it will check to see if
are fresh. If not, Dagster will bundle them in the next job run. • That also applies to manually running assets. I could just manually select
to be run as a single job. I think I see where in the tutorial you might get the impression that the whole dbt project needs to be run as a block. I’m not sure I understand what’s meant by “These assets share the same underlying op”, but regardless, dbt models are just loaded as any other assets with their list of dependencies. Was that even the question you were asking? 🙂
Noam Finkelstein01/26/2023, 6:43 PM
Loads a set of dbt models from a dbt project into Dagster assets.
Creates one Dagster asset for each dbt model. All assets will be re-materialized using a singleor
Olivier Dupuis01/26/2023, 8:50 PM
Noam Finkelstein01/26/2023, 8:56 PM
My worry is that because all the dbt assets share a single op,
slow_asset -> dbt_asset1 fast_asset -> dbt_asset2
can't be kicked off until
is done, even though all it really needs is for
to be done. Do you see what I mean?
Olivier Dupuis01/26/2023, 9:25 PM
owen01/26/2023, 10:46 PM
Noam Finkelstein01/27/2023, 4:20 PM
class and the
parameter, and lean into giving dagster full flexibility in terms of scheduling execution. We'll have a lot of data flowing in and out of the database, so dealing with a blocking dbt call would be inefficient. It's good to know what the options are!