as to 1) you have to define your request handler with a leading /, as in name= "/partItemNoSearch". Don't forget to restart your server.
3) Of course. The input terms MUST be run through the associated analysis chain to have any hope of matching correctly. Best Erick On Fri, Apr 13, 2012 at 8:36 AM, geeky2 <gee...@hotmail.com> wrote: > thank you for the response. > > it seems to be working well ;) > > 1) i tried your suggestion about removing the qt parameter - > > *somecore/partItemNoSearch*&q=dishwasher&debugQuery=on&rows=10 > > but this results in a 404 error message - is there some configuration i am > missing to support this short-hand syntax for specifying the requestHandler > in the url ? > > > > 2) ok - good suggestion. > > > > 3) yes it looks like it IS searching across all three (3) fields. > > i noticed that for the itemNo field, it reduced the search string from > dishwasher to dishwash - it this because of stemming on the field type, used > for the itemNo field? > > <lst name="debug"><str name="rawquerystring">dishwasher</str><str > name="querystring">dishwasher</str><str > name="parsedquery">+DisjunctionMaxQuery((brand:dishwasher^0.5 | > *itemNo:dishwash* | productType:dishwasher^0.8))</str><str > name="parsedquery_toString">+(brand:dishwasher^0.5 | itemNo:dishwash | > productType:dishwasher^0.8)</str> > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/searching-across-multiple-fields-using-edismax-am-i-setting-this-up-right-tp3906334p3907875.html > Sent from the Solr - User mailing list archive at Nabble.com.
