Hmm, this was fixed by restarting Solr. When does Solr/Lucene check for index file formats? We switched from a Lucene 1.9 index to a Lucene 2.4 index without a restart. Could that cause this?
wunder On 1/8/09 11:40 AM, "Walter Underwood" <wunderw...@netflix.com> wrote: > I'm seeing a really weird problem with Solr 1.3. The best match for a > query will not show up with 10 rows, but will show up if I request more, > sometimes 200, sometimes it takes 1000 rows. > > I tried increasing the row size by 10 and with some of those increments, > the first hit would change to a more relevant result. > > Here is the other weird part -- we have been running the indexing > system with Solr 1.1 and distributing those indexes to the 1.3 > query servers. This showed up when we converted the index server > to 1.3. Luckily, we have not done that in production. > > Here is the relevant part of solrconfig. Note that we have added a > JaroWinkler fuzzy search, so the dismax specs have extra decoration. > > <requestHandler name="groups" class="solr.SearchHandler"> > <lst name="defaults"> > <str name="defType">dismax</str> > <str name="echoParams">none</str> > <float name="tie">0.01</float> > <str name="qf"> > > exact^6.0 exact_alt^6.0 exact_base~jw_0.7_1^8.0 exact_alias^8.0 > title^3.0 title_alt^3.0 title_base^4.0 > </str> > <str name="pf"> > exact^9.0 exact_alt^9.0 exact_base^12.0 exact_alias^12.0 title^3.0 > title_alt^4.0 title_base^6.0 > </str> > <str name="bf"> > search_popularity^100.0 > </str> > <str name="mm">1</str> > <int name="ps">100</int> > > </lst> > <lst name="appends"> > <str name="fq">type:group</str> > </lst> > </requestHandler> > > > wunder > > >
