Michael Lunøe created MESOS-7291:
------------------------------------
Summary: Resolving a tasks path is involved and fragile for the
UI, could we get a separate endpoint to get this information?
Key: MESOS-7291
URL: https://issues.apache.org/jira/browse/MESOS-7291
Project: Mesos
Issue Type: Improvement
Components: agent, master
Reporter: Michael Lunøe
Right now we need to search through frameworks (active and completed), and it's
executors (active and completed) and match ids with fields on the task in order
to construct the path:
https://github.com/dcos/dcos-ui/blob/3a03770217757163c1fd24d51fb83cd9f18104d7/src/js/utils/MesosStateUtil.js#L210
I think it would make sense for Mesos to own this knowledge and expose an
endpoint to provide us with this information.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
