spuru9 opened a new pull request, #28756:
URL: https://github.com/apache/flink/pull/28756
## What is the purpose of the change
Backport of #28712 (FLINK-40118) to `release-2.3`.
The job Timeline tab's SubTask view and the SubTask Accumulators table both
render `N - undefined` instead of the TaskManager location for each subtask.
FLINK-36355 (#25436) removed the deprecated `host` field from the REST API's
subtask-level responses, keeping only `endpoint`, before Flink 2.0 shipped. The
web-dashboard frontend was never updated to match, so `task.host` has read
`undefined` on every 2.x release.
## Brief change log
- Update `JobSubTaskTime` (`job-timeline.ts`) and `SubTaskAccumulators`
(`job-accumulators.ts`) to declare `endpoint` instead of `host`.
- Update the two consumers — `job-timeline.component.ts` (SubTask TimeLine
chart labels) and `job-overview-drawer-accumulators.component.html` (SubTask
Accumulators table) — to read `endpoint`.
## Verifying this change
- Clean cherry-pick of the master fix (`npm run lint` / `npm run build` pass
on master, verified there against a running JobManager).
- Confirmed the bug is present on this branch: the backend REST models
(`SubtasksTimesInfo`, `SubtaskExecutionAttemptDetailsInfo`,
`SubtasksAllAccumulatorsInfo`) already emit only `endpoint`, so the frontend's
`task.host` was reading a field that no longer exists.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no (bug fix)
- If yes, how is the feature documented? not applicable
## AI Usage Disclosure
- [x] Claude Code
--
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]
