Hi Nathaniel, This is a bug. I might get around to fixing it but I can't promise anything. I'm focusing entirely on the C extension version of Ferret (which doesn't have this bug).
Cheers, Dave PS: Sorry for the slow reply. It's been a tough few weeks here. On 4/3/06, Nathaniel Talbott <[EMAIL PROTECTED]> wrote: > I've run in to an issue that I'm not sure how to address. Basically, I'm > building queries with occur_default Search::BooleanClause::Occur::MUST, > and using the StandardAnalyzer which does stop filtering. The stop > filtering is working beautifully on the indexing side. The problem is > that when the query parser parses through a query with a stop word in > it, say "the oregon trail", it builds a query that looks something like > this: > > MUST title: <blank> > MUST title: oregon > MUST title: trail > Which unfortunately fails when searching for the previously indexed "The > Oregon Trail" because it doesn't have a blank title term in it. > > Is there a good way to deal with this issue besides filtering stop words > before handing the query string off to the parser? > > Thanks! > > > Nathaniel > > P.S. I'm using the pure Ruby part of Ferret 0.9.0 on Ruby 1.8.4. > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Ferret-talk mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ferret-talk > _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
