The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

image.png

Hi, can someone help me?
I'm using this to make a dependency between a asset and my dbt_assets, but it's like not doing anything, because when the dbt_assets loads, they're after the table names I gave, not the asset I defined

following this example, dagster would want the assetkey jaffle_shop not snowflake, jaffle_shop and orders

Hey <@U03MXV86UNS>! Does your upstream asset key have any prefixes like the one in the example, or is it just `"my_asset_key"`? I assume you're looking to tie one asset to one source table?

With the previous example, I wasn't sure if you want/need a partition of not?

No, Brandon, I was about to go here and say my findings

While using a multi partitioned job, it only considers that the date 2024-02-02 was materialized when all the static partitions are also materialized and I just needed two static partitions

The reason of all my pain and suffering was my own memory not remembering this detail