eve the default setting! Rather, it should tell you how to
override the default setting.
-- Jack Krupansky
-Original Message-
From: Ahmet Arslan
Sent: Wednesday, February 19, 2014 4:16 AM
To: solr-user@lucene.apache.org
Subject: Re: Weird behavior of stopwords in search query
Hi Sami
Hi Samik,
Please see parameter of edismax.
https://cwiki.apache.org/confluence/display/solr/The+Extended+DisMax+Query+Parser
If lowercaseOperators=true then and is treated as AND. Also stopwords parameter
could be used.
Stopwords and edismax had issues (when mm=100%) in history. Not sure curren
Jack, thanks for the pointer. I should have checked this closely. I'm using
edismax and here's my qf entry :
id^10.0 cat^1.4 text^0.5 features^1.0 name^1.2 sku^1.5 manu^1.1
title^10.0 description^5.0 keywords^5.0 author^2.0 resourcename^1.0
As you can see, I was boosting id and
Does "other" appear in the id, cat, or sku fields? This clause requires it
to appear in at least one of those fields:
+DisjunctionMaxQuery((id:other^10.0 | cat:other^1.4 | sku:other^1.5))
The "and" is treated as the "AND" operator. What query parser are you using?
Without "and", the terms are
