A thread with this same subject from 2008/2009 is here: http://search-lucene.com/m/jkBgXnSsla
We're seeing customers being bitten by this "bug" now and then, and normally my workaround is to simply not use stopwords at all. However, is there an actual fix in the 3.1 eDisMax parser which solves the problem for real? Cannot find a JIRA issue for it. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com
