If I empty the stopword file and re-index, all expected matches happen. So maybe that provides a further suggestion of where the problem is. This certainly feels like a Solr bug (or lucene bug?).
-Peter On Sat, Mar 27, 2010 at 3:05 PM, Peter Wolanin <peter.wola...@acquia.com> wrote: > Hi Mitch, > > I am also seeing this locally with the exact same solr.war, > solrconfig.xml, and schema.xml running under Jetty, as well as on 2 > different production servers with the same content indexed. > > So this is really weird - this seems to be influenced by the surrounding text: > > "would be great to have support for Identi.ca on the follow block" > > fails to match "Identi.ca", but putting the content on its own or in > another sentence: > > "Support Identi.ca" > > the search matches. More testing suggests the word "for" is the > problem. I don't see an exception or error. Could be a problem with > how stopwords are removed? > > -Peter > > > On Sat, Mar 27, 2010 at 1:19 PM, MitchK <mitc...@web.de> wrote: >> >> Hi Peter, >> >> have you tried to reindex your data and did you do a commit? >> If you changed anything, have you restarted your Solr-server? >> >> I can't understand why this problem occurs, since the example seem to work >> at analysis.jsp. >> >> Kind regards >> - Mitch >> -- >> View this message in context: >> http://n3.nabble.com/Solr-1-4-bug-search-fails-but-analyzer-indicates-a-match-tp680066p680313.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > > > > -- > Peter M. Wolanin, Ph.D. > Momentum Specialist, Acquia. Inc. > peter.wola...@acquia.com > -- Peter M. Wolanin, Ph.D. Momentum Specialist, Acquia. Inc. peter.wola...@acquia.com
