Hello 👋, I can't find how we can link the source tables of a dbt project to assets that are created in ops using AssetMaterialization events. Since the asset names are known at run-time, does it mean that the assets can't be shown in the DAGs in the UI? Can Dagster use the materialization events in order to know that some upstream dependency of the DBT project has been updated? Thanks!

What I did on my setup was a custom function under

node_info_to_asset_key

to map my assets to dbt sources. It works since I’m not using `op`s, but have my entire platform based around assets. I’m not 100% sure on this, but I’d assume you can still map the materialization events to the dbt sources by passing the right key to the

AssetMaterialization

event, i.e.

AssetMaterialization(asset_key=AssetKey(["my", "dbt", "source", "key"]))

Hey Felix - if you have a dbt source named "asset0" and a model named "asset1" that depends on it, you should see something like this in your asset graph:

Thanks @sandy

I just tried this out, and it appears that the answer is no. Out of curiosity, why use ops + AssetMaterialization events instead of assets?

Hey @sandy, thanks for the answer! To address your question, ops + AssetMaterialization events felt more natural than assets for our particular use case. It's a bit hard to explain succinctly, but the main reason is that the tables are loaded incrementally and in many small chunks with dynamically optimized chunk sizes at runtime