We use solr 1.2 on our production environment so it seems like this was fixed in 1.3; let me try getting 1.3 and see if that fixes it: the only issue is convincing our IT team to move to 1.3 for production might not be that easy :(.
-Sachin -- "Yonik Seeley" <[EMAIL PROTECTED]> wrote: I can't reproduce this with Solr 1.3 http://localhost:8983/solr/select?q=%2b(text:solr)+%2b(text:of)+%2b(text:works)&debugQuery=true&rows=0 And the relevant fragment of the debugQuery is: <str name="rawquerystring">+(text:solr) +(text:of) +(text:works)</str> <str name="querystring">+(text:solr) +(text:of) +(text:works)</str> <str name="parsedquery">+text:solr +text:work</str> <str name="parsedquery_toString">+text:solr +text:work</str> -Yonik On Tue, Sep 16, 2008 at 7:20 PM, Sachin <[EMAIL PROTECTED]> wrote: > We use the StopFilterFactory with the stopwords.txt provided as part of the > solr getting started example and just realized that if the stop word is > enclosed within a parentheses then solr just strips out the stop word and not > the parens and this causes 0 results being returned. for example: trying > (text:solr) +(text:of) +(text:works) query with debug enabled returns the > parsed query as text:solr +() +text:work (notice the blank parentheses after > solr stripped out "of"). We use bracketed search quite a lot for grouping > query parts into logical group and this one always acts as a bummer; as > anytime the user enters one of the stop words he gets no results back. Is > there something obvious that I am missing here? ____________________________________________________________ Click here to save cash and find low rates on auto loans. http://thirdpartyoffers.netzero.net/TGL2231/fc/Ioyw6ijmyuWlIUsN1LhNQUee6Ea7EkxxrRiJxEPZBoOG819ppVjkm9/
