[
https://issues.apache.org/jira/browse/MESOS-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468633#comment-15468633
]
Zhitao Li commented on MESOS-5029:
----------------------------------
My opinion is this is just an oversight. IMHO, before the strong typed V1 API,
we don't really define a schema of what each JSON based endpoints should
return, so these information is very easy to miss unless the committer or
contributor can remember everything relating to a field.
[~StephanErb], can you please file a JIRA to add this information for whatever
endpoint you think this should be included?
For V1 API: this is much better because what each endpoint is supposed to
return is explicitly defined. Unfortunately we didn't include {{ExecugtorInfo}}
in {{GetContainers.Container message}} in
https://github.com/apache/mesos/blob/master/include/mesos/v1/agent/agent.proto.
[~vinodkone], can you evaluate on whether we should add {{ExecutorInfo}} in
response of {{GetContainters}}, or explicit ask the caller to double fetch?
> Add labels to ExecutorInfo
> --------------------------
>
> Key: MESOS-5029
> URL: https://issues.apache.org/jira/browse/MESOS-5029
> Project: Mesos
> Issue Type: Improvement
> Reporter: Zhitao Li
> Assignee: Zhitao Li
> Priority: Minor
> Labels: uber
> Fix For: 1.0.0
>
>
> We want to to allow frameworks to populate metadata on ExecutorInfo object.
> An use case would be custom labels inspected by QosController.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
