Attach &debug=query to the URL when you fire this query and you'll see exactly how it parses which should help you diagnose the problem. Some places to look:
1> There are options that treat lower case operators as valid. Normally, Solr only treats 'AND' as an operator not 'and' but this can be overridden. Really shouldn't be the case in quoted strings, but you never know. 2> stopwords. It's possible the "and" is just being removed and you're matching "Conceal some_other_stopword Carry". 3> are the quotes actually getting through the parsed query as you expect? Best, Erick On Mon, Feb 13, 2017 at 8:36 AM, Kameron Cole <kameronc...@us.ibm.com> wrote: > I have noticed odd behavior in the query > > "Conceal and Carry" > > I have legal customers who need to find exactly this phrase because, as > you know, it refers to a specific set of gun laws. > > However, this query is not behaving like a traditional quoted query - my > assumption is that a quoted string is not in any way manipulated by the > search engine. Yet, this query is definitely behaving like a boolean AND > query. In other words, the results are "Conceal" AND "Carry". The > assumption would be that you would get only documents with the exact > phrase "Conceal and Carry" > > Is there a built-in mechanism that finds operators/stop-words within > quoted queries? > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
