Because your query is "q=Champion Croissance" there is
another parameter to take care of.
It is "sow" which could be true or false.
Just search through the jira issues with edismax, mm and sow
to get any reports about it.
Regards
Bernd
Am 16.03.22 um 18:40 schrieb Dominique Bejean:
Hi Shawn,
For both dismax and edismax, documentation explain q.op is used only if mm
is not set and q.op=and is equal to mm=100% and q.op=or is equal to mm=0%.
It works fine with dismax but strangely but not with edismax in Solr 8.
Regards
Dominique
Le mer. 16 mars 2022 à 18:29, Shawn Heisey <apa...@elyograg.org> a écrit :
On 3/16/22 04:52, Dominique Bejean wrote:
I have some strange results when using both mm and q.op with edismax in
solr 8.11. In this case it looks like q.op has priority on mm.
In all other cases (solr 4 with both dismax and edismax ou Solr 8 with
dismax) in accordance with the documentation, mm has priority on q.op.
Here is my query and the results with generated parsedquery
defType=dismax or edismax
&mm=20%
&q.op=AND
&q=Champion Croissance
&qf=title_exact^0.9 title_srch^0.6% text_exact^0.5 text_srch^0.2
I believe setting q.op=AND sets mm to 100%. And I wouldn't be surprised
if that takes priority over an explicit mm setting.
Pick one or the other, and it should probably be mm with edismax/dismax.
The q.op parameter is more relevant for the lucene query parser, which
doesn't support mm.
Thanks,
Shawn
