spuru9 opened a new pull request, #28712:
URL: https://github.com/apache/flink/pull/28712

   ## What is the purpose of the change
   
   The job Timeline tab's SubTask view and the SubTask Accumulators table both 
render `N - undefined` instead of the TaskManager location for each subtask.
   
   ## Brief change log
   
   - FLINK-36355 removed the deprecated `host` field from the REST API's 
subtask-level responses (`SubtasksTimesInfo`, 
`SubtaskExecutionAttemptDetailsInfo`, `SubtasksAllAccumulatorsInfo`), keeping 
only `endpoint`. That PR (apache/flink#25436) touched only backend Java 
classes; the web-dashboard frontend was never updated to match, so `task.host` 
has read `undefined` since Flink 2.0.
   - 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 `task.endpoint` / `subTaskAccumulator.endpoint`.
   
   ## Verifying this change
   
   - `npm run lint` and `npm run build` pass.
   - Verified against a real running JobManager (local standalone cluster + 
StateMachineExample): before the fix, the Timeline tab's SubTask view showed `0 
- undefined`; after the fix, it shows `0 - localhost:<port>`.
   
   ## 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]

Reply via email to