You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2017/04/07 12:50:42 UTC
[jira] [Commented] (MESOS-7368) Documentation of framework role(s)
in proto definition is confusing
[ https://issues.apache.org/jira/browse/MESOS-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960730#comment-15960730 ]
Benjamin Bannier commented on MESOS-7368:
-----------------------------------------
[~guoger] [~bmahler]: I see you introduced {{deprecated}} and {{EXPERIMENTAL}} in {{eb674bb614}} and {{d06d05c76e}}, respectively. Could you coordinate on a resolution?
> Documentation of framework role(s) in proto definition is confusing
> -------------------------------------------------------------------
>
> Key: MESOS-7368
> URL: https://issues.apache.org/jira/browse/MESOS-7368
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Benjamin Bannier
>
> The documentation for role-related fields in {{FrameworkInfo}} is confusing: the {{role}} field is marked as {{deprecated}} while the {{roles}} field is marked as {{EXPERIMENTAL}} and has an additional {{NOTE}} advising to not use this field.
> This leaves users confused what field they should use in their code. Depending on how the proto definition is used {{deprecated}} might even produce (fatal) errors, while {{roles}} seems strongly discouraged.
> We should clean this up to make sure users always know which field they should use.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)