Lee-W commented on code in PR #66584: URL: https://github.com/apache/airflow/pull/66584#discussion_r3292205556
########## airflow-core/docs/authoring-and-scheduling/event-scheduling.rst: ########## @@ -64,6 +64,128 @@ event-driven scheduling, then a new trigger must be created. This new trigger must inherit ``BaseEventTrigger`` and ensure it properly works with event-driven scheduling. It might inherit from the existing trigger as well if both triggers share some common code. +Sharing one poll across sibling triggers +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.. versionadded:: 3.3 + +When several ``AssetWatcher`` instances on different assets back triggers that read from the **same upstream resource** +— a directory of flag files, a polling REST endpoint, a Kafka topic with auto-commit, and similar idempotent or +subscriber-side-effect sources — the triggerer would otherwise spin up one independent poll loop per trigger. For a +shared source with twenty subscribers that means twenty poll loops, twenty connections, twenty sets of API calls per +cadence. See "Suitable upstreams" below for the precise scope. Review Comment: Sounds good. just removed. thanks! -- 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]
