Skip to content

Conversation

@jedcunningham
Copy link
Member

@jedcunningham jedcunningham commented Sep 9, 2022

When we go to schedule dagruns from the dataset dagrun queue, we assume the events will happen before the queue records, which isn't the case unless we explicitly flush them first. This ensures that dagruns are properly related to their upstream dataset events.

Fixes #26256

When we go to schedule dagruns from the dataset dagrun queue, we assume
the events will happen before the queue records, which isn't the case
unless we explicitly flush them first. This ensures that dagruns are
properly related to their upstream dataset events.
@boring-cyborg boring-cyborg bot added the area:Scheduler including HA (high availability) scheduler label Sep 9, 2022
@jedcunningham jedcunningham added changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..) AIP-48 labels Sep 9, 2022
@jedcunningham jedcunningham merged commit 954349a into apache:main Sep 9, 2022
@jedcunningham jedcunningham deleted the dataset_event_dagrun_rel branch September 9, 2022 20:15
jedcunningham added a commit that referenced this pull request Sep 12, 2022
When we go to schedule dagruns from the dataset dagrun queue, we assume
the events will happen before the queue records, which isn't the case
unless we explicitly flush them first. This ensures that dagruns are
properly related to their upstream dataset events.

(cherry picked from commit 954349a)
@ephraimbuddy ephraimbuddy added this to the Airflow 2.4.0 milestone Sep 14, 2022
@eladkal eladkal added area:data-aware-scheduling assets, datasets, AIP-48 and removed AIP-48 labels Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:data-aware-scheduling assets, datasets, AIP-48 area:Scheduler including HA (high availability) scheduler changelog:skip Changes that should be skipped from the changelog (CI, tests, etc..)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"triggered runs" dataset counter doesn't update until *next* run and never goes above 1

4 participants