Thomas:
If you go to the admin UI, pick a collection (or core) and go to the
"analysis" page. Put different values in the "index" and "query" entry
boxes. Sometimes a picture is worth a thousand words ;).
And, indeed, synonyms are one of the prime filters that are often
different between the
You're welcome, great to hear you have less doubts.
I see you're using the SynonymGraphFilter followed by a StopFilter at
query time: have a look at this post [1], you might find some useful info.
Best,
Andrea
[1] https://sease.io/2018/07/combining-synonyms-and-stopwords.html
On 15/08/18
Hi Andrea,
Thanks so much. I wasn¹t thinking in the correct perspective on the query
portion of the analyzer, but your explanation makes perfect sense. In my
head I imagine the result set of the query being transformed by the
filters, but in actuality the filter is being applied to the query
Hi Thomas,
as you know, the two analyzers play in a different moment, with a
different input and a different goal for the corresponding output:
* index analyzer: input is a field value, output is used for building
the index
* query analyzer: input is a (user) query string, output is used
Hi,
We have the text field below configured on fields that are both stored and
indexed. It seems to me that applying the same filters on both index and query
would be redundant, and perhaps a waste of processing on the retrieval side if
the filter work was already done on the index side. Is
