You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, using @multi_asset_sensor, is it possible to monitor assets that are materialized in a code location A, but the jobs to launch and the sensor are defined in a code location B ? Is there a way to achieve this ?
@multi_asset_sensor(monitored_assets=AssetSelection.groups("codelocA"), # In code location Aname="dbt_codelocA",description="code loc A sensor",jobs=[code_loc_B_job_1, code_loc_B_job_2, code_loc_B_job_3], # in code location B)defdbt_codelocA(context: MultiAssetSensorEvaluationContext):
asset_events=context.latest_materialization_records_by_key()
ifall(asset_events.values()):
context.advance_all_cursors()
yieldRunRequest(job_name="code_loc_B_job_1")
yieldRunRequest(job_name="code_loc_B_job_2")
yieldRunRequest(job_name="code_loc_B_job_3")
I've done my test and AssetSelection.groups("codelocA"), gives me {}, while my dbt job materializing codelocA is working super fine and the assets are well defined in code location A
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, using @multi_asset_sensor, is it possible to monitor assets that are materialized in a code location A, but the jobs to launch and the sensor are defined in a code location B ? Is there a way to achieve this ?
I've done my test and AssetSelection.groups("codelocA"), gives me {}, while my dbt job materializing codelocA is working super fine and the assets are well defined in code location A
Beta Was this translation helpful? Give feedback.
All reactions