-
Notifications
You must be signed in to change notification settings - Fork 13.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
Update airflow tasks *
commands to lookup TaskInstances from DagRun Table
#16030
Conversation
It looks like a breaking change. Am I right? |
The Workflow run is cancelling this PR. Building images for the PR has failed. Follow the workflow link to check the reason. |
I can't really tell right now. From what I understand, the execution date sent to the tasks command is not really used in the context of execution date but to just get TaskInstance. I will shed more light as I work on this. Update: |
2836b62
to
3dbfdb3
Compare
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.
(small changes, fuller review comming)
90ef73f
to
b20b0f1
Compare
ef5ea57
to
4bf8983
Compare
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
…tances from DagRun Table
Co-authored-by: Ash Berlin-Taylor <ash_github@firemirror.com>
Co-authored-by: Ash Berlin-Taylor <ash_github@firemirror.com>
This change removes execution_date from task commands and uses DagRun.run_id instead
…from DagRun Table
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
a056f8f
to
0bca458
Compare
0bca458
to
df6293b
Compare
This change adds the ability to lookup TaskInstances using the DagRun.run_id
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.