Introduce DeltaTriggerTimetable #46846
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
uranusjr
force-pushed
the
switch-default-literal-interpretation
branch
6 times, most recently
from
ac1afd5 to
91b7335
Compare
This completes the matrix of trigger vs data interval, and cron vs delta expression timetables. The goal is to replace 'schedule' expressions where currently the data interval timetables are used to use trigger timetables instead, e.g. 'schedule=timedelta(days=1)'. Trigger timetables do not have data intervals (by default), and also have a more intuitive logical date representation. This is a lot more intuitive not only for Airflow newcomers, but also existing users that do not care about data intervals, but use DAGs as a workflow that simply runs periodically. Don't do timetable equality Fix doc refs
uranusjr
force-pushed
the
switch-default-literal-interpretation
branch
from
91b7335 to
a1c6b20
Compare
sunank200
approved these changes
Feb 24, 2025
phanikumv
approved these changes
Feb 25, 2025
jedcunningham
pushed a commit
to astronomer/airflow
that referenced
this pull request
Feb 25, 2025
This completes the matrix of trigger vs data interval, and cron vs delta expression timetables. The goal is to replace 'schedule' expressions where currently the data interval timetables are used to use trigger timetables instead, e.g. 'schedule=timedelta(days=1)'. Trigger timetables do not have data intervals (by default), and also have a more intuitive logical date representation. This is a lot more intuitive not only for Airflow newcomers, but also existing users that do not care about data intervals, but use DAGs as a workflow that simply runs periodically. Don't do timetable equality Fix doc refs
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 28, 2025
This completes the matrix of trigger vs data interval, and cron vs delta expression timetables. The goal is to replace 'schedule' expressions where currently the data interval timetables are used to use trigger timetables instead, e.g. 'schedule=timedelta(days=1)'. Trigger timetables do not have data intervals (by default), and also have a more intuitive logical date representation. This is a lot more intuitive not only for Airflow newcomers, but also existing users that do not care about data intervals, but use DAGs as a workflow that simply runs periodically. Don't do timetable equality Fix doc refs
nailo2c
pushed a commit
to nailo2c/airflow
that referenced
this pull request
Apr 4, 2025
This completes the matrix of trigger vs data interval, and cron vs delta expression timetables. The goal is to replace 'schedule' expressions where currently the data interval timetables are used to use trigger timetables instead, e.g. 'schedule=timedelta(days=1)'. Trigger timetables do not have data intervals (by default), and also have a more intuitive logical date representation. This is a lot more intuitive not only for Airflow newcomers, but also existing users that do not care about data intervals, but use DAGs as a workflow that simply runs periodically. Don't do timetable equality Fix doc refs
39 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This completes the matrix of trigger vs data interval, and cron vs delta expression timetables. The goal is to replace 'schedule' expressions where currently the data interval timetables are used to use trigger timetables instead, e.g. 'schedule=timedelta(days=1)'.
Trigger timetables do not have data intervals (by default), and also have a more intuitive logical date representation. This is a lot more intuitive not only for Airflow newcomers, but also existing users that do not care about data intervals, but use DAGs as a workflow that simply runs periodically.
If this sounds like a good idea, I will create two subsequent PRs to switch the configs (so trigger timetables are used by default), and to backport the timetable to 2.11 for migration.