[
https://issues.apache.org/jira/browse/MESOS-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135228#comment-15135228
]
Michael Park commented on MESOS-4582:
-------------------------------------
[~marco-mesos] I've already looked it up, and the presence of duplicate keys is
valid JSON. Many JSON libraries (Go, Python, C#, etc) simply use the last
instance of the duplicate keys. Those same libraries make it hard (impossible?)
to generate a JSON with duplicate keys. My proposal here is to take the same
approach where we are tolerant of input with duplicate keys, but don't generate
JSON with duplicate keys in our output.
> state.json serving duplicate "active" fields
> --------------------------------------------
>
> Key: MESOS-4582
> URL: https://issues.apache.org/jira/browse/MESOS-4582
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.27.0
> Reporter: Michael Gummelt
> Assignee: Michael Park
> Priority: Blocker
> Attachments: error.json
>
>
> state.json is serving duplicate "active" fields in frameworks. See the
> framework "47df96c2-3f85-4bc5-b781-709b2c30c752-0000" In the attached file
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
