You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First step in AIP-86 to add Deadline Alerts. Plenty more to come, but I wanted to break it down into reasonable bites for easier review.
This PR adds the new Deadline field to the DAG database table, a new model to handle the Deadline, and the unit tests to cover those additions. The next PR (already queued up once this is merged) will implement the DeadlineTrigger class which I sketched out in this one.
^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.
* Add deadline to DAG model
Example usage:
```
@task
def hello():
log.info('hello world')
with DAG(
dag_id='dag_with_deadline',
deadline=DeadlineAlert(
trigger=DeadlineTrigger.DAGRUN_LOGICAL_DATE,
interval=timedelta(hours=1),
callback=hello_callback,
)
):
hello()
```
This was removed in #50093 -- I assume by mistake! Adding this back to not break das of people migration from Airflow 2.x
(cherry picked from commit 9cd9c9f)
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
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.
First step in AIP-86 to add Deadline Alerts. Plenty more to come, but I wanted to break it down into reasonable bites for easier review.
This PR adds the new Deadline field to the DAG database table, a new model to handle the Deadline, and the unit tests to cover those additions. The next PR (already queued up once this is merged) will implement the DeadlineTrigger class which I sketched out in this one.
Example usage:
^ 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 airflow-core/newsfragments.