On Tue, Nov 30, 2010 at 7:51 PM, Martin Grotzke <martin.grot...@googlemail.com> wrote: > On Tue, Nov 30, 2010 at 3:09 PM, Yonik Seeley > <yo...@lucidimagination.com> wrote: >> On Tue, Nov 30, 2010 at 8:24 AM, Martin Grotzke >> <martin.grot...@googlemail.com> wrote: >>> Still I'm wondering, why this issue does not occur with the plain >>> example solr setup with 2 indexed docs. Any explanation? >> >> It's an old option you have in your solrconfig.xml that causes a >> different code path to be followed in Solr: >> >> <!-- An optimization that attempts to use a filter to satisfy a search. >> If the requested sort does not include score, then the filterCache >> will be checked for a filter matching the query. If found, the filter >> will be used as the source of document ids, and then the sort will be >> applied to that. --> >> <useFilterForSortedQuery>true</useFilterForSortedQuery> >> >> Most apps would be better off commenting that out or setting it to >> false. It only makes sense when a high number of queries will be >> duplicated, but with different sorts. > > Great, this sounds really promising, would be a very easy fix. I need > to check this tomorrow on our test/integration server if changing this > does the trick for us. I just verified this fix on our test/integration system and it works - cool!
Thanx a lot for this hint, cheers, Martin