msumit opened a new pull request, #71220: URL: https://github.com/apache/airflow/pull/71220
**Value prop**: As a centralised platform team, we don't want end users to give control of this field, especially when they are totally unaware of what `deferred` really means here. For them, pool slots are used to control the load on the downstream systems like Spark and Presto, and it doesn't matter whether that task is deferred or not. So with a cluster level config we'll take control of the behaviour. **Changes**: Introduced a new configuration option `core.pool_include_deferred`. When set to `True` or `False`, it fixes the effective value for every pool (including pre-existing pools) and prevents users from setting a conflicting per-pool value via the UI, API, or CLI. The default remains unset (empty string `""`), preserving the existing per-pool behavior. Updated the pool model, local/FastAPI API serializers, UI config endpoint and pool form, CLI pool commands, default pool creation, and added corresponding tests. - When config is set to `True` <img width="914" height="525" alt="Screenshot 2026-08-06 at 10 04 57 AM" src="https://github.com/user-attachments/assets/75baa0e1-25ef-4910-aeea-11fb405ba722"; /> - When config is set to `False` <img width="909" height="529" alt="Screenshot 2026-08-06 at 10 06 03 AM" src="https://github.com/user-attachments/assets/090aad81-11ee-4b8a-826c-56e9c41c9960"; /> - When someone tries to set an opposite value via API <img width="1413" height="754" alt="Screenshot 2026-08-06 at 12 48 05 PM" src="https://github.com/user-attachments/assets/033b4847-d1df-4314-93d4-5ca5cdecb570"; /> - When API doesn't contain any info regarding to this flag <img width="1405" height="714" alt="Screenshot 2026-08-06 at 12 48 37 PM" src="https://github.com/user-attachments/assets/7e4bf982-eb37-4eaa-9204-76e41b6d3176"; /> <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: https://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. For user-facing UI changes, please attach before/after screenshots (or a short screen recording) so reviewers can assess the visual impact. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [x] Yes - Generated by Claude <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
