takayoshi-makabe opened a new pull request, #69178:
URL: https://github.com/apache/airflow/pull/69178
Keys containing `/` (e.g. `"spark/job_id"`) silently fail with 404 when
accessed through the Execution API used by running tasks. The routes were
defined with `{key}` instead of `{key:path}`, so FastAPI treated the slash as a
path separator and could not match the route.
The Public API (used by UI/external clients), defined in
`airflow-core/src/airflow/api_fastapi/core_api/routes/public/task_state_store.py`,
already uses `/{key:path}` and is correct. This PR aligns the Execution API
(`airflow-core/src/airflow/api_fastapi/execution_api/routes/task_state_store.py`)
with that existing pattern.
---
##### Was generative AI tooling used to co-author this PR?
- [x] Yes (please specify the tool below)
Claude Code
---
* 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]
