Makoto
07/30/2021, 11:44 PMprha
07/31/2021, 12:34 AMAssetMaterialization
event with an AssetKey
that the pipeline B sensor is listening for (though it could certainly do both).Makoto
07/31/2021, 12:53 AMchrispc
07/31/2021, 5:30 PMprha
08/02/2021, 3:35 PM@asset_sensor
decorator. You could then update the cursor if and only if all of the A, B, C pipelines have emitted their corresponding materializations. I believe there’s some example code in the documentation for this: https://docs.dagster.io/concepts/partitions-schedules-sensors/sensors#multi-asset-sensorschrispc
08/02/2021, 3:38 PMAndrew Brown
08/11/2021, 4:50 PM@run_status_sensor
decorator to kick off a pipeline B upon successful completion of a pipeline A. Is that possible? I don’t see how yielding a RunRequest would work in this case, since the @run_status_sensor
decorator does not take a pipeline_name
parameter to target for requested runs.