: This isn't a problem in Lucene or Solr. It is a result of the analyzers
: you have chosen to use. If you choose to remove stopwords, you will not
: be able to match stopwords.

I believe paul's point was that this use of stopwords is in the "text" 
fieldtype in the example schema.xml ... which many people use as is.

I'm personally of the mindset that it's fine like it is.  While people who 
understand that "an" is a stop word might ask "why does 'rating:PG AND 
name:an' match 40K movies, it should match 0?" there is another (probably 
larger) group of people who won't know how the search is implemented, or 
that "an" is a stop word, and they will look at the same results and ask 
"why am i getting 40K results? most of these don't have 'an' in the title? 
i should only be getting X results."

That second group of people aren't going to be any happier if you 
give them 0 results instead -- at least this way people get some results 
to work with.


-Hoss

Reply via email to