-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
AIP-61 - Add executor field to the task instance API #40034
Conversation
Return executor as part of TaskInstance queries and also enable filtering by executor field. Also use the changes to display the executor field on the TaskInstance Details web page.
I'm not sure why some provider tests are failing around fab imports/tests. I didn't modify anything around there. But this is my first API changes so perhaps someone else knows? CC @bbovenzi, you and I chatted about this change a couple weeks back |
Looks good - with one NIT - we should at least discuss if we need an index, as per discussion in https://lists.apache.org/thread/sg08mcdmvvtrwpd5cccpkl198do0xlc6 |
It looks like the failing test was resolved in #39899. This should be good to merge @o-nikolas? |
Please rebase first. |
Return executor as part of TaskInstance queries and also enable filtering by executor field. Also use the changes to display the executor field on the TaskInstance Details web page. Co-authored-by: Vincent <[email protected]>
Return executor as part of TaskInstance queries and also enable filtering by executor field.
Also use the changes to display the executor field on the TaskInstance Details web page.
Some screenshots of the API working both with curl and in the weberver task instance details page:
First task run with an executor overridden to "apple" (an example alias):
Second task run without an executor override (so the default executor is used):
^ 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 newsfragments.