That's a bit "fast" to expect somebody to reproduce this from information given. Or even in general to check the mailing list, given that we are not paid support :-)
Could you please 1) Download the latest 8.0 distribution 2) Do one of the basic examples 3) Give the search query that shows before/after BQ 4) Bonus points: test the same thing in 7.4 again with the same example This allows somebody to reproduce the situation exactly without wondering if it was something already fixed after 7.4, or an issue in your example or something else. Regards, Alex. On Tue, 16 Apr 2019 at 13:17, Nicolas Franck <nicolas.fra...@ugent.be> wrote: > > any update on this? > > > On 5 Mar 2019, at 09:06, Nicolas Franck <nicolas.fra...@ugent.be> wrote: > > > > I noticed a change in the behaviour of the regular "dismax" parser. > > At least in version 7.4: > > > > when you add "bq", it filters the results (like "fq" does), instead of > > boosting the matches. > > > > > > e.g. > > > > defType=dismax > > bq=format:periodical^30 > > > > gives only records with format "periodical". > > removing the parameter "bq" returns all records > > > > It does work when defType is set to "edismax". > > > > Any idea? >
