[
https://issues.apache.org/jira/browse/SOLR-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2292:
------------------------------
Fix Version/s: (was: 3.1)
Next
Moving out all unassigned issues set to 3.1 per this email:
http://www.lucidimagination.com/search/document/f026cc56081b5a51/unassigned_jira_issues_set_for_3_1
> Lock down NamedList API, remove inefficent and esoteric methods
> ---------------------------------------------------------------
>
> Key: SOLR-2292
> URL: https://issues.apache.org/jira/browse/SOLR-2292
> Project: Solr
> Issue Type: Task
> Reporter: Hoss Man
> Fix For: Next
>
>
> Over in SOLR-2288, rmuir made some good points about locking down the
> NamedList API to protect people...
> {quote}
> I looked at your patch, and personally I think NamedList should really be
> type-safe.
> If users want to use it in a type-unsafe way, thats fine, but *the container
> itself shouldn't be List<Object>*.
> {quote}
> ...
> {quote}
> Separately, i just want to say the following about NamedList:
> All uses of this API should really be reviewed. I'm quite aware that it warns
> you about the fact that its slow for certain operations,
> but in my opinion these *slow operations such as get(String, int) should be
> deprecated and removed*.
> Any users that are using NamedList in this way, especially in loops, are very
> likely using the wrong datastructure.
> {quote}
> (emphasis added by me)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
