...

• SubtasksAllAccumulatorsHandler
• SubtasksTimesHandler
• SubtaskCurrentAttemptDetailsHandler (corresponds to the subtasks details panel of a job vertex on UI)

• JobVertexTaskManagersHandler (corresponds to theTaskManger details panel of a job vertex on UI)

• JobExceptionsHandler

Proposed Changes

1. Add a new string formatter method to TaskManagerLocation and ArchivedTaskManagerLocation that prints in the form of "${hostname}:${port}" to align the string formatter used by REST API.
2. Use a field named "location" (already used in JobExceptionsInfoWithHistory) that represents TaskManager location in the form of "${hostname}:${port}" in a consistent mannerusing the newly added string formatter method.
3. Update the front-end to adopt the new location field.
4. Rename the column name from "Host" to "Location" on the Web UI to reflect the change that both hostname and port are displayed.
5. Keep the old "host" field untouched for compatibility. Notice that the info stored in the old "host" field is inconsistent, sometimes only host is stored, sometimes host + port is stored, we 'll leave them as they were with a few comments to keep being compatible.

...

The the old "host" fields in REST API is left untouched for compatibility, they will be marked as deprecated and can be removed in the next major version (2.0after being kept for at least 2 minot releases).

Test Plan

UTs and simple human-involved tests on UI should cover it well.

...