lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Search phrase not parsed properly
Date Sat, 11 Jan 2020 02:03:49 GMT
The easiest way to verify this is to use the admin UI. Select a core (or replica), go to the
analysis page. Select the field in question from there and type the words into the textbox.
I’d also uncheck the “verbose” box, the detailed information resulting from that is

Do note that this is showing you what happens to your input _after_ parsing, so if you type
in query AND will, it’ll think the “AND” is just a word, not an operator. But it’ll
tell you whether the schema you actually use, rather than what you think you’re using is
dropping the “will” and what filter does that if so.


> On Jan 10, 2020, at 8:36 PM, Edward Ribeiro <> wrote:
> You have to check your managed-schema to see if the field type defines a
> stopwordfilter and which one it points to.
> There's a folder named 'lang' with many files, one for each language. If
> your field is configured to english the filter will point to
> lang/stopword_en.txt. The stopwords.txt file is empty by default. Also, you
> can test this by using the Analysis option in Admin UI.
> Best,
> Edward
> Em sex, 10 de jan de 2020 22:26, chester <>
> escreveu:
>> I checked the stopwords.txt file and it is empty. That means "will" is
>> not a
>> stop word, correct?
>> --
>> Sent from:

View raw message