Deprecate implicit default DAG schedule #41321
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
Currently, if a DAG is created with the 'schedule' argument, Airflow sets the DAG to run daily. This is almost never what people want, and every best practice tells you to always specify the argument explicitly, but we couldn't change the default due to compatibility considerations. We can finally change this in Airflow 3.0, but first we need to tell users about it.
kaxil
approved these changes
Aug 7, 2024
jscheffl
approved these changes
Aug 7, 2024
uranusjr
requested review from
dstandish,
ephraimbuddy and
jedcunningham
as code owners
jscheffl
reviewed
Aug 7, 2024
jedcunningham
approved these changes
Aug 8, 2024
uranusjr
force-pushed
the
deprecate-missing-schedule
branch
from
fe49f6c to
2de04c7
Compare
vincbeck
approved these changes
Aug 8, 2024
uranusjr
force-pushed
the
deprecate-missing-schedule
branch
from
2f54b65 to
d12b93d
Compare
uranusjr
changed the title
Contributor
I raised #41457 to document the protocols |
uranusjr
force-pushed
the
deprecate-missing-schedule
branch
from
a72b193 to
210df42
Compare
Member
Author
|
Finally… now merge and work on bacporting. |
uranusjr
added a commit
to astronomer/airflow
that referenced
this pull request
Aug 15, 2024
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
2 tasks
Contributor
|
s/with/without a ‘schedule’ argument. |
Artuz37
pushed a commit
to Artuz37/airflow
that referenced
this pull request
Aug 19, 2024
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Aug 20, 2024
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
utkarsharma2
added
the
changelog:skip
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 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.
Currently, if a DAG is created without the 'schedule' argument, Airflow sets the DAG to run daily. This is almost never what people want, and every best practice tells you to always specify the argument explicitly, but we couldn't change the default due to compatibility considerations.
We can finally change this in Airflow 3.0, but first we need to tell users about it.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.