[
https://issues.apache.org/jira/browse/SOLR-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984960#comment-15984960
]
Shawn Heisey commented on SOLR-10522:
-------------------------------------
I haven't looked at the code, but if I had to guess, I would imagine that the
internal representation is NamedList, which doesn't have a problem with
multiple mappings where the key is the same.
Do we need to deal with backward compatiblity at all, or do we consider the new
format to be completely broken? Were XML and Javabin responses also affected
by SOLR-9972?
> Duplicate keys in "collations" object with JSON response format
> ---------------------------------------------------------------
>
> Key: SOLR-10522
> URL: https://issues.apache.org/jira/browse/SOLR-10522
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: spellchecker
> Affects Versions: 6.5
> Reporter: Nikita Pchelintsev
> Priority: Minor
>
> After upgrading Solr 6.3 -> 6.5 I've noticed a change in how json response
> writer outputs "collations" response key when spellchecking is enabled
> (wt=json&json.nl=arrarr)
> Solr 6.3:
> "collations":
> [
> ["collation",{
> "collationQuery":"the",
> "hits":48,
> "maxScore":"30.282",
> "misspellingsAndCorrections":
> [
> ["thea","the"]]}],
> ["collation",{
> "collationQuery":"tea",
> "hits":3,
> "maxScore":"2.936",
> "misspellingsAndCorrections":
> [
> ["thea","tea"]]}],
> ...
> Solr 6.5:
> "collations":{
> "collation":{
> "collationQuery":"the",
> "hits":43,
> "misspellingsAndCorrections":
> [
> ["thea","the"]]},
> "collation":{
> "collationQuery":"tea",
> "hits":3,
> "misspellingsAndCorrections":
> [
> ["thea","tea"]]},
> ...
> Solr 6.5 outputs object instead of an array, and it has duplicate keys which
> is not valid for JSON format.
> Any help is appreciated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
