Hi community,
During integration tests with new data source I have noticed weird scenario
where replacement character can't be searched, though, seems to be stored.
I mean, honestly, I don't want that irrelevant data stored in my index but
I wondered if solr can index replacement character (U+FFFD
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
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.
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",