[ 
https://issues.apache.org/jira/browse/MESOS-6993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Park updated MESOS-6993:
--------------------------------
    Description: 
When sending roles back to frameworks (within Resource.role or 
Resource.allocation_info.role), we need translate the role back to the format 
the framework used when subscribing to the role. That is, if the framework did 
not use a leading slash or used “\*”, we will omit the leading slash and 
convert the “/” role to “\*”.

This is required to ensure backwards compatibility with schedulers that 
continue to use the non-hierarchical role format.

  was:
When sending roles back to frameworks (within Resource.role or 
Resource.allocation_info.role), we need translate the role back to the format 
the framework used when subscribing to the role. That is, if the framework did 
not use a leading slash or used “*”, we will omit the leading slash and convert 
the “/” role to “*”.

This is required to ensure backwards compatibility with schedulers that 
continue to use the non-hierarchical role format.


> Translate hierarchical roles back to the old format for non-hierarchical role 
> schedulers.
> -----------------------------------------------------------------------------------------
>
>                 Key: MESOS-6993
>                 URL: https://issues.apache.org/jira/browse/MESOS-6993
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Benjamin Mahler
>
> When sending roles back to frameworks (within Resource.role or 
> Resource.allocation_info.role), we need translate the role back to the format 
> the framework used when subscribing to the role. That is, if the framework 
> did not use a leading slash or used “\*”, we will omit the leading slash and 
> convert the “/” role to “\*”.
> This is required to ensure backwards compatibility with schedulers that 
> continue to use the non-hierarchical role format.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to