vincbeck commented on issue #50369: URL: https://github.com/apache/airflow/issues/50369#issuecomment-2872323667
> Is the general pattern going to be to build a Trigger, and leverage the out-of-the-box airflow.sdk.AssetWatcher when defining an Asset? Or instead, would a user/contributor define a custom Asset Watcher that has a baked-in Trigger. It is definitely the former. The idea is, any trigger extending `BaseEventTrigger` can be used to schedule DAGs. `AssetWatcher` is only a wrapper on top of the trigger, essentially it allows to name the trigger. This will be useful for #48017. The more triggers extending `BaseEventTrigger` there are available, the more options users will have to schedule their DAGs based on events. > How will we pass information from an AssetWatcher object to downstream Tasks in a DAG? Will this always be via context['triggering_asset_events'] ...? The most obvious example would be a file lands in an object store, and we want to process it. `AssetWatcher` does not pass any information to downstream tasks, again this is just a thin wrapper on top of the trigger. On the other side, the trigger can pass information to the downstream tasks using the event. Using `triggering_asset_events`, you can fetch the events that triggered the DAG, so any information you pass when sending the event in the trigger, can be fetch in tasks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
