lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Assigned] (SOLR-6780) Merging request parameters with defaults produce duplicate entries
Date Thu, 27 Nov 2014 01:29:13 GMT


Hoss Man reassigned SOLR-6780:

    Assignee: Hoss Man

> Merging request parameters with defaults produce duplicate entries
> ------------------------------------------------------------------
>                 Key: SOLR-6780
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.1, 5.0, Trunk
>            Reporter: Alexandre Rafalovitch
>            Assignee: Hoss Man
>              Labels: parameters
>         Attachments: SOLR-6780.patch
> When a parameter (e.g. echoParams) is specified and overrides the default on the handler,
it actually generates two entries for that key with the same value. 
> Most of the time it is just a confusion and not an issue, however, some components will
do the work twice. For example faceting component as described in
> It may also be connected to SOLR-6369
> The cause seems to be the interplay between *DefaultSolrParams#getParameterNamesIterator()*
which just returns param names in sequence and *SolrParams#toNamedList()* which uses the first
(override then default) value for each key, without deduplication.
> It's easily reproducible in trunk against schemaless example with 
> bq. curl "http://localhost:8983/solr/schemaless/select?indent=true&echoParams=all"
> I've also spot checked it and it seems to be reproducible back to Solr 4.1.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message