Versions Compared

Old Version 5

changes.mady.by.user Zhanghao Chen

Saved on

compared with

New Version Current

changes.mady.by.user Zhanghao Chen

Saved on

Key

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

...

Page properties

Document the state by adding a label to the FLIP page with one of "discussion", "accepted", "released", "rejected".

Discussion threadhttps://lists.apache.org/thread/sls1196mmk25w8nm2qf585254nbjr9hd
Vote threadhere (<- link to https://lists.apache.org/list.html?dev@flink.apache.org)
JIRAhere (<- link to https://issues.apache.org/jira/browse/FLINK-XXXX)
thread/rx435kvxctn6z6nf165vrg5c19nlpwcf
JIRA


Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-33146
Release1.19Release<Flink Version>


Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

...

  • 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 Add a new string formatter method getEndpoint() to TaskManagerLocation and ArchivedTaskManagerLocation that prints in the form of "${hostname}:${port}" in a consistent mannerto align the string formatter used by REST API.
  2. Use a field named "endpoint" that represents TaskManager endpoint (host + port) using the newly added string formatter method.
  3. Update the front-end to adopt the new location endpoint field.
  4. Rename the column name from "Host" to "LocationEndpoint" 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.

...