Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor DAG.dataset_triggers into the timetable class #39321

Merged
merged 1 commit into from
Jun 27, 2024

Conversation

uranusjr
Copy link
Member

This allows us to remove a bunch of conditionals regarding whether a DAG is backed by a timetable or dataset condition, and a weird edge case in serialization where we don't actually deserialize datasets in a timetable.

Now datasets are always serialized as a part of the timetable, and we always evaluate the timetable and datasets. Timetables that do not actually contain datasets (most of them) simply always evaluate to False.

@uranusjr uranusjr force-pushed the dag-schedule-refactor branch from 2dbc042 to e926a8c Compare April 30, 2024 11:45
@uranusjr uranusjr changed the title Shorten base dataset protocol name Refactor DAG.dataset_triggers into the timetable class Apr 30, 2024
@uranusjr uranusjr force-pushed the dag-schedule-refactor branch 3 times, most recently from e06212b to 54fdeb7 Compare April 30, 2024 14:20
@uranusjr uranusjr marked this pull request as ready for review April 30, 2024 15:12
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Jun 15, 2024
@uranusjr uranusjr removed the stale Stale PRs per the .github/workflows/stale.yml policy file label Jun 17, 2024
Copy link
Member

@Lee-W Lee-W left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, but would be great if we could have one or two more eyes on this one

@eladkal eladkal added this to the Airflow 2.10.0 milestone Jun 27, 2024
@eladkal eladkal added the type:improvement Changelog: Improvements label Jun 27, 2024
Copy link
Contributor

@eladkal eladkal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Needs rebase

This allows us to remove a bunch of conditionals regarding whether a DAG
is backed by a timetable or dataset condition, and a weird edge case in
serialization where we don't actually deserialize datasets in a
timetable.

Now datasets are always serialized as a part of the timetable, and we
always evaluate the timetable and datasets. Timetables that do not
actually contain datasets (most of them) simply always evaluate to
False.
@uranusjr uranusjr force-pushed the dag-schedule-refactor branch from 54fdeb7 to 058718b Compare June 27, 2024 06:37
@uranusjr uranusjr merged commit d0e4b8d into apache:main Jun 27, 2024
52 checks passed
@uranusjr uranusjr deleted the dag-schedule-refactor branch June 27, 2024 09:47
romsharon98 pushed a commit to romsharon98/airflow that referenced this pull request Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants