Skip to content
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

Merged
merged 3 commits into from
Jun 14, 2024

Conversation

o-nikolas
Copy link
Contributor

@o-nikolas o-nikolas commented Jun 4, 2024

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):

executor_curl_api_request

executor_webserver_task_details_api

Second task run without an executor override (so the default executor is used):

executor_webserver_task_details_api_no_exec_override


^ 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.

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.
@boring-cyborg boring-cyborg bot added area:API Airflow's REST/HTTP API area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues labels Jun 4, 2024
@o-nikolas o-nikolas changed the title Add executor field to the task instance API AIP-61 - Add executor field to the task instance API Jun 4, 2024
@o-nikolas
Copy link
Contributor Author

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

@o-nikolas o-nikolas added this to the Airflow 2.10.0 milestone Jun 4, 2024
@potiuk
Copy link
Member

potiuk commented Jun 13, 2024

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

@syedahsn
Copy link
Contributor

It looks like the failing test was resolved in #39899. This should be good to merge @o-nikolas?

@uranusjr
Copy link
Member

Please rebase first.

@potiuk potiuk merged commit c2959c9 into apache:main Jun 14, 2024
50 checks passed
@vincbeck vincbeck deleted the onikolas/aip-61/ti_exec_api branch June 14, 2024 14:58
@utkarsharma2 utkarsharma2 added the type:improvement Changelog: Improvements label Jul 1, 2024
romsharon98 pushed a commit to romsharon98/airflow that referenced this pull request Jul 26, 2024
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:API Airflow's REST/HTTP API area:hybrid-executors AIP-61 area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues type:improvement Changelog: Improvements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants