vincbeck commented on issue #49857: URL: https://github.com/apache/airflow/issues/49857#issuecomment-2834557250
I confirm everything that has been said here. `example_asset_with_watchers` might not be the best example and I might replace with a real world scenario. A paused DAG will never be executed if it receives an event (because it is paused). If you want to emit event -> store event -> process event then you might want to use a queue. It needs to be configured outside of Airflow. You configure you env to be send to a queue of choice and then you, in Airflow, your configure your DAG to be executed whenever a new message lands in the queue. Today only SQS is available (with `SqsMessageQueueProvider`) as queue provider to be compatible with event driven scheduling but other providers should be soon available. > Other question, during my tests I guess that one time between the time that dags was paused and the trigger stop whatching for file, the /tmp/test was deleted but no asset event was generated, but since I was not able to find which part of code manage the return of trigger and create the asset event I was not able to push more investigation. Could you tell me where I can find these code ? https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/assets/manager.py#L109 -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
