I can reproduce it.

I added your parameters to the default section of the config and then
run the following:
curl 
"http://localhost:8983/solr/schemaless/select?q=*:*&rows=0&wt=json&indent=true&facet=true&facet.field=primaryId2&facet.limit=10&echoParams=all";

I get:
------------------
   "params":{
      "f.typedef.facet.limit":"15",
      "facet.field":"primaryId2",
      "df":"_text",
      "f.subtype.facet.limit":"15",
      "echoParams":"all",
      "facet.mincount":"1",
      "rows":"0",
      "facet":"true",
      "q":"*:*",
      "facet.limit":"10",
      "facet.field":"primaryId2",
      "indent":"true",
      "echoParams":"all",
      "rows":"0",
      "wt":"json",
      "facet":"true"}},
------------------

This is against Solr 5 build, but I think that bug is there all the
way to Solr 4.1. I think I traced the source of the bug too (parameter
and default names are just joined together but with the first
(override) value both times as shown above). Usually makes no
difference to anything, but it looks like faceting component iterates
over the elements, not just gets them, so it gets bitten twice.

I've created a JIRA for this issue:
https://issues.apache.org/jira/browse/SOLR-6780

Regards,
   Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/ and @solrstart
Solr popularizers community: https://www.linkedin.com/groups?gid=6713853


On 21 November 2014 at 18:29, Alexandre Rafalovitch <arafa...@gmail.com> wrote:
> Could you add echoParams=all to the query and see what comes back?
> Currently, you echo the params you sent, would be good to see what
> they look like after they combine with defaults.
>
> Regards,
>   Alex.
> Personal: http://www.outerthoughts.com/ and @arafalov
> Solr resources and newsletter: http://www.solr-start.com/ and @solrstart
> Solr popularizers community: https://www.linkedin.com/groups?gid=6713853
>
>
> On 21 November 2014 18:04, Tom Zimmermann <zimm.to...@gmail.com> wrote:
>> Brian and I are working together to diagnose this issue so I can chime in
>> quickly here as well. These values are defined as part of the the defaults
>> section of the config.

Reply via email to