: I was under understanding that stopwords are filtered even before being
: parsed by search handler, i do have the filter in collection schema to
: filter stopwords and the analysis shows that this stopword is filtered
Generally speaking, your understanding of the order of operations for
query parsing (regardless of hte parser) and analysis (regardless of the
fields/analyzers/filters/etc...) is backwards.
the query parser gets, as it's input, the query string (as a *single*
string) and the request params. it inspects/parses the string according
to it's rules & options & syntax and based on what it finds in that string
(and in other request params) it passes some/all of that string to the
analyzer for one or more fields, and uses the results of those analyzers
as the terms for building up a query structure.
ask yourself: if the raw user query input was first passed to an analyzer
(for stop word filtering as you suggest) before the being passed to the
query parser -- how would solr know what analyzer to use? in many parsers
(like lucene and edismax) the fields to use can be specified *inside* the
query string itself
likewise: how would you ensure that syntactically significant string
sequences (like "(" and ":" and "AND" etc..) that an analyzer might
normally strip out based on the tokenizer/tokenfilters would be preserved
so that the query parser could have them and use them to drive hte
resulting query structure?
-Hoss
http://www.lucidworks.com/
