[
https://issues.apache.org/jira/browse/AURORA-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503396#comment-14503396
]
Bill Farner commented on AURORA-1284:
-------------------------------------
Looks like this differentiation is lost in a rather distant part of the system,
when we first translate {{Protos.Attribute}} to our internal {{Attribute}}:
https://github.com/apache/aurora/blob/895d03ba60a2bfd8bd24dbbeaef484ba7bf9cad3/src/main/java/org/apache/aurora/scheduler/base/Conversions.java#L128-L129
I suppose you could consider what you see on /slaves to be a reflection of how
Aurora is dealing with them, as it will be semantically the same for the two
ways of expressing it on the slave command line.
> /slaves should distinguish lists from comma separated values
> ------------------------------------------------------------
>
> Key: AURORA-1284
> URL: https://issues.apache.org/jira/browse/AURORA-1284
> Project: Aurora
> Issue Type: Task
> Reporter: Brian Brazil
> Priority: Minor
>
> The mesos slave attributes dedicated=A;dedicated=B and dedicated=A,B both
> render as dedicated=[A,B] on the /slaves end point of the Aurora scheduler.
> This is a little confusing, I'd suggest that the list render as
> dedicated=[A],[B] to distinguish these.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
