On Fri, Jan 28, 2011 at 3:00 PM, Thumuluri, Sai <sai.thumul...@verizonwireless.com> wrote: > I recently upgraded to Solr 1.4.1 from Solr 1.3 and with the upgrade > used edismax query parser. Here is my solrconfig.xml . When I search for > "mw verification and payment information" - I get no results with > defType set to edismax,
It's probably a bit of natural language query parsing in edismax... - and is treated as AND (the lucene operator) in the appropriate context (i.e. we won't if it's at the start or end of the query, etc) - or is treated as OR in the appropriate context The lowercaseOperators parameter can control this, so try setting lowercaseOperators=false -Yonik http://lucidimagination.com > if I switch the deftype to dismax - I get the results I am looking for > > Can anyone explain, why this would be the case? I thought edismax is > dismax and more. > > Thank you, > > For 1.4.1 > <requestHandler name="partitioned" class="solr.SearchHandler" > default="true"> > <lst name="defaults"> > <str name="defType">dismax</str> > <str name="echoParams">explicit</str> > <float name="tie">0.01</float> > <str name="qf"> > body^1.0 title^10.0 name^3.0 taxonomy_names^2.0 tags_h1^5.0 > tags_h2_h3^3.0 tags_h4_h5_h6^2.0 tags_inline^1.0 > </str> > <str name="pf"> > body^10.0 > </str> > <int name="ps">4</int> > <str name="mm"> > 2<-25% > </str> > <str name="q.alt">*:*</str> > > <str name="hl">true</str> > <str name="hl.fl">body</str> > <int name="hl.snippets">3</int> > <str name="hl.mergeContiguous">true</str> > <!-- instructs Solr to return the field itself if no query terms are > found --> > <str name="f.body.hl.alternateField">body</str> > <str name="f.body.hl.maxAlternateFieldLength">256</str> > <!--<str name="f.body.hl.fragmenter">regex</str>--> <!-- defined > below -- > > Sai Thumuluri
