You should not leave it in the qf field. You’re getting confused by the
difference between query _parsing_ and the analysis chain. The parsing turns
your top-level query of “ice cream” (assuming without quotes) into something
like
f1:ice f1:cream f2:ice f2:cream
This is happening way before an
Thanks Erick, that seems to work!
Should I leave it in qf also? For example the query "blue dog" may be
represented as separate tokens in the keyword index.
On Mon, Sep 30, 2019 at 9:32 PM Erick Erickson
wrote:
> Have you tried taking your keyword field out of the “qf” param and adding
> it e
Have you tried taking your keyword field out of the “qf” param and adding it
explicitly? As keyword:”ice cream”
Best,
Erick
> On Sep 30, 2019, at 5:27 AM, Ashwin Ramesh wrote:
>
> Hi everybody,
>
> I am using the edismax parser and have noticed a very specific behaviour
> with how sow=true (d
Hi everybody,
I am using the edismax parser and have noticed a very specific behaviour
with how sow=true (default) handles multiword keywords.
We have a field called 'keywords', which uses the general
KeywordTokenizerFactory. There are also other text fields like title and
description. etc.
When
