Hi Chris, This is on Sorl 8.1.1
I think by "what query parser" you mean this: <fieldType name="test_text" class="solr.TextField" autoGeneratePhraseQueries="true" positionIncrementGap="100"> <analyzer> <tokenizer class="solr.WhitespaceTokenizerFactory"/> <filter class="solr.WordDelimiterFilterFactory" catenateNumbers="1" generateNumberParts="1" stemEnglishPossessive="1" splitOnCaseChange="0" generateWordParts="1" splitOnNumerics="1" preserveOriginal="1" catenateAll="1" catenateWords="1"/> <filter class="solr.LowerCaseFilterFactory"/> <filter class="solr.RemoveDuplicatesTokenFilterFactory"/> </analyzer> </fieldType> By "request parameter" I think you are asking what I'm sending to Solr? if sow I'm sending it the raw text of "or" or "OR". In case you mean my request-handler, it is this: {"requestHandler":{"/select_hcl":{ "class":"solr.SearchHandler", "name":"/select_hcl", "defaults":{ "defType":"edismax", "echoParams":"explicit", "fl":"CC_UNIQUE_FIELD,CC_FILE_PATH,score", "indent":"true", "qf":"CC_ALL_FIELDS_DATA", "rows":"100", "wt":"xml"}}}} Yes, I'm using edismax. So if that's what's causing it, how do I tell it to treat only uppercase OR and AND as operators? Thanks in advanced. Steven On Wed, Aug 7, 2019 at 7:39 PM Chris Hostetter <hossman_luc...@fucit.org> wrote: > > what version of solr? > what query parser are you using? > what do all of your request params (including defaults) look like? > > it's possible you are seeing the effects of edismax's "lowercaseOperators" > param, which _should_ default to "false" in modern solr, but > in very old versions it defaulted to "true" (inspite of what the docs at > the time said)... > > > https://lucene.apache.org/solr/guide/8_1/the-extended-dismax-query-parser.html > https://issues.apache.org/jira/browse/SOLR-4646 > > > : Date: Wed, 7 Aug 2019 19:32:02 -0400 > : From: Steven White <swhite4...@gmail.com> > : Reply-To: solr-user@lucene.apache.org > : To: solr-user@lucene.apache.org > : Subject: Lower case "or" is being treated as operator OR? > : > : Hi everyone, > : > : My schema is setup to index all words (no stop-words such as "or", "and", > : etc.) are removed. My default operator is AND. But when I search for > "one > : or two" (without the quotes as this is not a phrase search) I'm getting > : hits on documents that have either "one" or "two". It has the same > effect > : as if I searched for "one OR two". Any idea why? > : > : Where should I look to see what's causing this issue? What part of my > : schema or request handler do you need to see? > : > : In case this helps. Searching for just "or" or "OR" (with or without > : quests) gives me the same set of hits and ranking. The same is also true > : for "and" or "AND". > : > : Thanks. > : > : Steven > : > > -Hoss > http://www.lucidworks.com/ >