Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Public Interfaces

Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed. The purpose of this section is to concisely call out the public contract that will come along with this feature.

Any handlers/interfaces in the entire REST API and Web UI that contains TaskManager location info.

  • 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. Use a field named "location" (already used in JobExceptionsInfoWithHistory) that represents TaskManager location in the form of "${hostname}:${port}" in a consistent manner.
  2. Update the front-end to adopt the new location field.
  3. Rename the column name from "Host" to "Location" on the Web UI to reflect the change that both hostname and port are displayed.
  4. 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.

Compatibility, Deprecation, and Migration Plan

...

...

The the old "host" fields in REST API is left untouched for compatibility, they can be removed in the next major version (2.0).

Test Plan

...

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

Rejected Alternatives

...

Not applicable.