[
https://issues.apache.org/jira/browse/SOLR-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254836#comment-14254836
]
Yonik Seeley commented on SOLR-6369:
------------------------------------
Yes, I think this bug was caused by SOLR-6780, but it's been fixed.
> duplicate json key "echoParams" should be removed in ping-response
> ------------------------------------------------------------------
>
> Key: SOLR-6369
> URL: https://issues.apache.org/jira/browse/SOLR-6369
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.9
> Environment: testing on ubuntu 14.04
> version: 4.9.0 1604085 - rmuir - 2014-06-20 06:34:03
> Reporter: Marc Portier
> Priority: Trivial
>
> Apparently the /admin/ping handler will duplicate the echoParams key in the
> json-response.
> $ curl -s http://localhost:8983/solr/test-node-client/admin/ping?wt=json
> {"responseHeader":{"status":0,"QTime":2,"params":{"df":"text","echoParams":"all","rows":"10","echoParams":"all","wt":"json","q":"solrpingquery","distrib":"false"}},"status":"OK"}
> Having "echoParams":"all" twice in that response doesn't really make sense?
> Strictly speaking this is allowed in the json spec, so it is not a violation
> in principle
> http://stackoverflow.com/questions/21832701/does-json-syntax-allow-duplicate-keys-in-an-object
> However there are some json-parse implementations out there that want to map
> this into hashtables and are not silently overwriting the key with the last
> seen value, but are throwing errors in the process.
> To those a cleanup of the json response would make life somewhat easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
