Under 4.10 q.op was ignored by the edismax parser and always forced to OR. 5.5 is looking at the q.op=AND you requested.
There are also some changes to the default values selected for mm, but I doubt those apply here since you are setting it explicitly. On 8 September 2016 at 00:35, Mikhail Khludnev <m...@apache.org> wrote: > I suppose > <str name="parsedquery_toString">+((text:star text:trek)~2)</str> > and > <str name="parsedquery_toString">+(+text:star +text:trek)</str> > are equal. mm=2 is equal to +foo +bar > > On Wed, Sep 7, 2016 at 10:52 AM, Bernd Fehling < > bernd.fehl...@uni-bielefeld.de> wrote: > > > Hi list, > > > > while going from SOLR 4.10.4 to 5.5.3 I noticed a change in query > parsing. > > 4.10.4 > > <str name="rawquerystring">text:star text:trek</str> > > <str name="querystring">text:star text:trek</str> > > <str name="parsedquery">(+((text:star text:trek)~2))/no_coord</str> > > <str name="parsedquery_toString">+((text:star text:trek)~2)</str> > > > > 5.5.3 > > <str name="rawquerystring">text:star text:trek</str> > > <str name="querystring">text:star text:trek</str> > > <str name="parsedquery">(+(+text:star +text:trek))/no_coord</str> > > <str name="parsedquery_toString">+(+text:star +text:trek)</str> > > > > There are very many new features and changes between this two versions. > > It looks like a change in query parsing. > > Can someone point me to the solr or lucene jira about the changes? > > Or even give a hint how to get my "old" query parsing back? > > > > Regards > > Bernd > > > > > > -- > Sincerely yours > Mikhail Khludnev >
