Daniel Galea
03/22/2023, 10:52 AM@asset(ins={"upstream_asset": AssetIn(key_prefix="one/two/three")})
def downstream_asset(upstream_asset):
return upstream_asset + [4]
However, in my case my downstream assets do not require the upstream asset as an input. I generally have one job which acts as an ingestion job and when that is done I explicitly materialize an asset which in turn triggers another job which is the transformation job and has a sensor that is triggered by that asset materialization. So materialization of asset 1 triggers the materialization of asset 2. I am not passing data from one step to the next in Dagster as I didn't want to couple my transformation code with it. How can I link assets but also not require passing them around?Rasmus Bonnevie
03/22/2023, 11:10 AMnon_argument_deps
parameter on the asset decorator which does exactly that 🙂 it's just a set of the asset keys you want as dependencies without passing data.Daniel Galea
03/22/2023, 12:08 PMRasmus Bonnevie
03/22/2023, 12:12 PMDaniel Galea
03/22/2023, 1:08 PM