Sorry, I was hurrying before class (training to get a service dog). I use the DisMax handler, which can expand a query to go against multiple fields. The per-field analysis applies at both index and query time, so the exact field does not have stopwords removed. Very helpful for queries like "Being There" or "To be and to have".
wunder On 5/14/08 10:54 AM, "cricdigs" <[EMAIL PROTECTED]> wrote: > > Hi wunder, > > Thanks for your response. I am still a little confused. Solr's analysis page > shows that the stop word is removed from the query - its got nothing to do > with the indexing imo. > > If indexing has removed the stop words then I should not get any results > right? But I get the results with the stop word removed. > > How do I tell Solr to send phrase queries to a field other than default? > Will I have to code that or is it just a config setting? > > Thanks. > > > Walter Underwood wrote: >> >> Try creating a separate field that does not remove stopwords, >> populating that with <copyfield> and configuring the phrase >> queries to go against that field instead. >> >> I do something similar. For both regular and phrase queries, >> we have a stemmed and stopped field and another field with >> neither. The "exact" field has a higher boost. This helps >> with movies like "Saw" and "Ran", which should not show >> "see" or "run" as the top match. >> >> wunder >> >> On 5/14/08 8:09 AM, "cricdigs" <[EMAIL PROTECTED]> wrote: >> >>> >>> Hi all, >>> >>> Is there a config setting that I could use to not remove stop words when >>> doing an exact phrase match. For example when searching for "the world" >>> (in >>> quotes) I would like to look for just that and not get results for just >>> "world". When I look at the analysis, I see that word "the" is removed by >>> the StopFilter even if it is in quotes. So is there a work-around to >>> solve >>> this? >>> >>> Thanks! >> >> >>
