Remove 'allow_trigger_in_future' config #46663
Merged
Conversation
This file contains 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
added
the
airflow3.0:breaking
boring-cyborg
bot
added
area:Scheduler
A DAG run with logical date in the future can never be started now. This only affects schedule=None, which can only be triggered manually. Instead of using a future date, you can trigger with a None logical date whenever you want. A custom run_id can be supplied if you want it. If a date is needed, it can be passed as a DAG param instead.
uranusjr
force-pushed
the
fix-logical-date-none-scheduler
branch
from
7512fb1 to
6f52ec2
Compare
uranusjr
force-pushed
the
fix-logical-date-none-scheduler
branch
from
6f52ec2 to
3ac9945
Compare
eladkal
approved these changes
Feb 12, 2025
Lee-W
approved these changes
Feb 12, 2025
|
I'll merge it and rebase it to #46460 once CI is green. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A DAG run with logical date in the future can never be started now. This only affects schedule=None, which can only be triggered manually.
Instead of using a future date, you can trigger with a None logical date whenever you want. A custom run_id can be supplied if you want it. If a date is needed, it can be passed as a DAG param instead.