Followup:
I had a theory that Nicky tested, and I think what was observed confirms the
theory.
TL;DR:
In previous versions, I think there was a bug where the presence of boolean
operators caused edismax to ignore the mm parameter, and only rely on the
boolean operator(s).
After that bug got
Hi,
What is your full query path or URL that you pass for the query?
And how is your setting like for the edismax in your solrconfig.xml?
Regards,
Edwin
On Fri, 26 Oct 2018 at 06:24, Nicky Mastin wrote:
>
> Oddity with edismax and queries involving boolean operators. Here's the
> "parsedquery
Oddity with edismax and queries involving boolean operators. Here's the
"parsedquery_toString" from two different queries:
input: "dog AND kiwi":
https://apaste.info/gaQl
input: "dog OR kiwi":
https://apaste.info/sBwa
Both queries return the same number of results (389). The query with OR was
