-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Conversation
2dbc042
to
e926a8c
Compare
e06212b
to
54fdeb7
Compare
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. |
There was a problem hiding this 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
There was a problem hiding this 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.
54fdeb7
to
058718b
Compare
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.