[
https://issues.apache.org/jira/browse/SOLR-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084130#comment-14084130
]
Yonik Seeley commented on SOLR-6315:
------------------------------------
I guess my confusion is why this is confusing at all...
I'l try to put it as succinctly as possible to try and reduce confusion:
{code}
If you want the data serialized as a "JSON Object", use SimpleOrderedMap.
Given that some clients will lose "JSON Object" ordering information, use
NamedList to serialize to something that will preserve order (e.g.
[key1,val1,key2,val2])
{code}
At the end of the day, this is really all about JSON and client / language
adapters. An unordered Map has a natural mapping to JSON... but something
where order is more important (represented by NamedList) does not. This is why
we picked one [k1,v1,k2,v2,...] but allowed it to be overridden by json.nl:
http://wiki.apache.org/solr/SolJSON#JSON_specific_parameters
If someone feels the javadoc needs to be improved, please put up a patch.
> Remove SimpleOrderedMap
> -----------------------
>
> Key: SOLR-6315
> URL: https://issues.apache.org/jira/browse/SOLR-6315
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Reporter: Shai Erera
> Assignee: Shai Erera
> Attachments: SOLR-6315.patch
>
>
> As I described on SOLR-912, SimpleOrderedMap is redundant and generally
> useless class, with confusing jdocs. We should remove it. I'll attach a patch
> shortly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
