Thanks for the reply.
So, as an aside, should I remove the solr.WhitespaceTokenizerFactory
and solr.WordDelimiterFilterFactory from the query analyzer part?
Any idea in which direction I should poke around? I deactivated dismax
for now, but would really like to use it.
Wouter Admiraal
2015
.
Just as a side-question: is dismax *supposed* to match fields exactly
with the search query? Or is my expectation correct, meaning it should
"tokenize" the field, just as with regular searches? It just doesn't
seem intuitive to me.
Thank you again for your help.
Kind regards,
Wouter
r": "DisMaxQParser",
"altquerystring": null,
"boostfuncs": null,
...
}
I don't understand how/why this doesn't use a "contains" operator.
This was the behavior on the old 1.4 instance. I went through the
changelog for 1.4 to 5.1, but I don't find any explicit information
about dismax behaving differently, except the "mm" parameter needs a
default. I tried many values for mm (including 0, 100%, 100, etc) but
to no avail.
Thanks for your help.
Best regards,
Wouter Admiraal
