I work with Meltano and DBT in Dagster. I am building assets from both meltano and dbt via multi_asset functionality. I am able to link Meltano Assets as upstream assets to DBT assets as per recommendation

By @sandy hey Binoy - do you have sources defined in dbt that correspond to the tables that are being created via Meltano? if so, that lineage should happen automatically
if the asset keys aren't lining up, you can use the node_info_to_asset_key or source_key_prefix argument of load_assets_from_dbt_project / load_assets_from_dbt_manifest to make it so they do (edited)

But I want to intercept the extract_load::meltano -> transform::dbt with some validations What I am looking for is extract_load:(meltano-assets) -->

@job/@op

Quality Check Job --> transform::(dbt-assets) -->

@job/@op

post-process

So, I don’t use meltano nor DBT, but if I’m understanding correctly here this doesn’t actually matter? Have you looked into using graph backed assets? Seems like this could be a single graph eg: extract -> Data quality check -> Transform -> post process

I haven’t. I will check it out now

Yeah, IIRC the dagster team is currently exploring more advanced ways of doing stuff like this with the more high level apis (like asset), but ATM the easiest way to get it done may to take one step down into jobs/ops/graphs then just wrap them in an asset.

Oh okay, that’s good insight.

Unfortunately, within graph-backed assets, we don't currently support having any ops that don't produce an asset output (or aren't upstream of an asset output). Though as Zach mentioned we are exploring higher level APIs to handle asset expectations. You could create the graph-backed asset for your meltano/dbt assets, and then output your data quality check as another asset.

Good to know, we’re currently doing the latter at the moment. (Move the data if it’s good, otherwise keep it in staging). Is there any roadmap for when some more of those asset expectations may start rolling out, or is it too early to say?

Oh okay, thanks for the clarification Claire

@Zach P I think it's still too early to say. We're definitely very interested in supporting asset expectations and I think it is something we will implement down the line, but it's not part of the immediate roadmap.

Makes sense! Looking forward to it 🙂