So, the stopwords.txt file is different between the two systems - the first has stop words but the second does not. Did you expect stop words to be removed, or not?

-- Jack Krupansky

-----Original Message----- From: Stavros Delsiavas
Sent: Wednesday, October 16, 2013 5:02 PM
To: solr-user@lucene.apache.org
Subject: Re: Local Solr and Webserver-Solr act differently ("and" treated like "or")

Okay I understand,

here's the rawquerystring. It was at about line 3000:

<lst name="debug">
 <str name="rawquerystring">title:(into AND the AND wild*)</str>
 <str name="querystring">title:(into AND the AND wild*)</str>
 <str name="parsedquery">+title:wild*</str>
 <str name="parsedquery_toString">+title:wild*</str>

At this place the debug output DOES differ from the one on my local
system. But I don't understand why...
This is the local debug output:

<lst name="debug">
  <str name="rawquerystring">title:(into AND the AND wild*)</str>
  <str name="querystring">title:(into AND the AND wild*)</str>
  <str name="parsedquery">+title:into +title:the +title:wild*</str>
  <str name="parsedquery_toString">+title:into +title:the
+title:wild*</str>

Why is that? Any ideas?




Am 16.10.2013 21:03, schrieb Shawn Heisey:
On 10/16/2013 4:46 AM, Stavros Delisavas wrote:
My local solr gives me:
http://pastebin.com/Q6d9dFmZ

and my webserver this:
http://pastebin.com/q87WEjVA

I copied only the first few hundret lines (of more than 8000) because
the webserver output was to big even for pastebin.



On 16.10.2013 12:27, Erik Hatcher wrote:
What does the debug output say from debugQuery=true say between the two?
What's really needed here is the first part of the <debug> section,
which has rawquerystring, querystring, parsedquery, and
parsedquery_toString.  The info from your local solr has this part, but
what you pasted from the webserver one didn't include those parts,
because it's further down than the first few hundred lines.

Thanks,
Shawn


Reply via email to