On Sat, 11 Apr 2020, Eran Buchnick wrote:
: Date: Sat, 11 Apr 2020 23:34:37 +0300
: From: Eran Buchnick
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Re: Required operator (+) is being ignored when using default
: conjunction operator AND
:
: Hoss
Hoss, thanks a lot for the informative response. I understood my
misunderstanding with infix and prefix operators. Need to rethink about the
term occurrence support in my search service.
Cheers!
On Mon, Apr 6, 2020, 20:43 Chris Hostetter wrote:
>
> : I red your attached blog post (and more) but
: I red your attached blog post (and more) but still the penny hasn't dropped
: yet about what causes the operator clash when the default operator is AND.
: I red that when q.op=AND, OR will change the left(if not MUST_NOT) and
: right clause Occurs to SHOULD - what that means is that the "order
Hoss, thanks a lot for the response.
OK, so it seems like I got into to the "uncanny valley" of the search
operators:/
I red your attached blog post (and more) but still the penny hasn't dropped
yet about what causes the operator clash when the default operator is AND.
I red that when q.op=AND, OR
: Using solr 8.3.0 it seems like required operator isn't functioning properly
: when default conjunction operator is AND.
You're mixing the "prefix operators" with the "infix operators" which is
always a recipe for disaster.
The use of q.op=AND vs q.op=OR in these examples only
complicates
Using solr 8.3.0 it seems like required operator isn't functioning properly
when default conjunction operator is AND.
Steps to reproduce:
20 docs
all have text field
17 have the value A
13 have the value B
10 have both A and B (the intersection)
===the data===
[
{
"id": "0",
