> Since "will" is on the stop list, this query will never return any
> documents. So I think this should be an error, the problem is that the
> error message is uninformative.
If the documents have been indexed with an analyzer that includes the
stop filter, then the queries should be preprocessed through the same
analyzer, otherwise a whole host of problems, like this one, could occur.
> That's a pretty complicated API! Does anyone have better ideas?
I think what QP needs to do here is run each discrete term through the
analyzer, and change its behavior based on that. For example, if the
input text is "+A", but the analyzer turns "A" into "B B" (dumb
example, but you get the idea) it needs to build a PhraseQuery, not a
TermQuery. Similarly, if the Analyzer eliminates A completely from
the token stream, then QP should drop that term from the resulting
Query that its building. In other words, have QP parse the query first,
and then run each sub-part through the analyzer, and adjust for the number
of tokens returned.
IIRC, currently QP is not very savvy when it comes to anything but
one-for-one transformations by the Analyzer.
_______________________________________________
Lucene-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/lucene-dev
