https://dagster.io/ logo
Title
y

Yeachan Park

10/28/2022, 3:00 PM
Hi all, we're trying to define a dependency between two graph backed assets. Each asset contains multiple OPs. After defining the asset dependency, the lineage correctly shows an upstream/downstream dependency between the two assets. However, while materializing the assets, without passing the upstream asset as an argument to an OP in the downstream asset, OPs in the downstream asset can get executed concurrently with OPs in the upstream asset. Is there a way the dependency can just be defined at the asset level, such that all OPs in the upstream asset must finish first without having to pass the upstream asset as an argument to a downstream OP to have it respect the order in which to execute the OPs? Thanks for your help!
j

jamie

10/28/2022, 3:40 PM
hi @Yeachan Park right now you have to pass the upstream outputs to the ops to define the dependency structure. Feel free to open a GH issue for your feature request though!
👍 1
y

Yeachan Park

10/28/2022, 3:41 PM
Thank you, will do