[
https://issues.apache.org/jira/browse/SOLR-12959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675863#comment-16675863
]
David Smiley commented on SOLR-12959:
-------------------------------------
Neither echoParams (a SolrParams) nor the stored fields (a SolrDocument) are
held as NamedLists and thus don't apply in your example. Nonetheless I get your
drift.
I wonder... in places where we are using SimpleOrderedMap in a response, and
thus the "access by key" is most significant... (i.e. it's map-ness is most
significant)... maybe we should just switch over to say LinkedHashMap? Keys
cannot repeat in a LinkedHashMap but the demands of the two seem to me to
compete with each other: ease of access by key & repeated keys are kinda
incompatible – better off using a list of values. I should spot-check some
SimpleOrderedMap usages in Solr to see how easily they might be redone as
LinkedHashMap.
As an aside, we're missing a "maparr" json.nl value that could represent values
inside arrays. But I suppose that could not be done in a streaming manner.
> Deprecate solrj SimpleOrderedMap
> --------------------------------
>
> Key: SOLR-12959
> URL: https://issues.apache.org/jira/browse/SOLR-12959
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Reporter: Noble Paul
> Priority: Minor
>
> There is no difference between a NamedList and a SumpleOrderedMap. It
> doesn't help to have both of them when they are doing exactly free same things
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
