ubject: Re: Edismax parser weird behavior
Hey Erick, Thanks to Jack I have a working solution to issue no 2. For 1 I'm
looking for a solution.
Please help me for that.
debug Query are as below:
Search for *auto*: 36 results: parsedquery:
"+DisjunctionMaxQuery((text:auto^0.2 | media_transcript:a
Right, examine the parsed query carefully and
you'll see that the semantics are much different.
At a guess, "auto" appears in more than one
field. So your first query is saying
"return me any documents for which "auto" appears
in any of the fields (text, media_transcript.).
Your NOT clause is
Hey Erick, Thanks to Jack I have a working solution to issue no 2. For 1 I'm
looking for a solution.
Please help me for that.
debug Query are as below:
Search for *auto*: 36 results: parsedquery:
"+DisjunctionMaxQuery((text:auto^0.2 | media_transcript:auto^0.4 |
title:auto^0.9 | keywords:auto^0.7
What do you get when you specify &debugQuery=on (&debug=query in 4.x)?
In other words, what does the parsed query look like?
Best
Erick
On Wed, Aug 22, 2012 at 8:13 AM, amitesh116 wrote:
> Hi I am experiencing 2 strange behavior in edismax:
> edismax is configured to behave default OR (using mm=
Don't have an immediate answer for you on #1, but for #2, "mm" does not
override explicit operators - "and" - it only applies to terms that are not
the immediate operand of an explicit operator. Note that by default
lower-case operators are enabled in edismax - "and" is treated as "AND" -
you c
