Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EF85510CE8 for ; Wed, 16 Oct 2013 10:28:35 +0000 (UTC) Received: (qmail 95859 invoked by uid 500); 16 Oct 2013 10:28:30 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 95806 invoked by uid 500); 16 Oct 2013 10:28:29 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 95794 invoked by uid 99); 16 Oct 2013 10:28:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Oct 2013 10:28:28 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of erik.hatcher@gmail.com designates 209.85.128.49 as permitted sender) Received: from [209.85.128.49] (HELO mail-qe0-f49.google.com) (209.85.128.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Oct 2013 10:28:22 +0000 Received: by mail-qe0-f49.google.com with SMTP id a11so400049qen.36 for ; Wed, 16 Oct 2013 03:28:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=I6Gc3GQ8E9Ao/nV6U42hWHvCrBqSw5Z16cbiysHbClU=; b=vYqEFEEGs+eqTd0HDWIxDCLTS8z/Bebu7ybwUyjBz+ydkltHrBKPB93C/miDhD/BIZ IvF6YCOhWnWElBnQngeBrBPdS2Q0r6sORPmk5xnxscgVF2z7VsD3IFSOACAA6fmkMx1O Go3QTEh+ezVt5VdrHUmDrxHJ+SbGx4qnirnMLnUv0mO0325z/gkBkad5dfc0MFN1GIOd mM73GcWjHq2iYSM88vUyBT93gzGSC0tR6F8HzJ1IjAy1VbIhGtnm5yn2+1G12zoVZfLn SBciz6aHMaRuv/LRpFWayEbtNNXeEfqvLkZCEAc3LRShWn9gPuKs7SPBkqHTOR61e3uu d0Kg== X-Received: by 10.224.32.66 with SMTP id b2mr3572873qad.80.1381919281528; Wed, 16 Oct 2013 03:28:01 -0700 (PDT) Received: from [10.0.1.10] (c-71-206-171-110.hsd1.va.comcast.net. [71.206.171.110]) by mx.google.com with ESMTPSA id kz8sm38754101qeb.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Oct 2013 03:28:00 -0700 (PDT) References: <525E597E.9010607@delisavas.de> Mime-Version: 1.0 (1.0) In-Reply-To: <525E597E.9010607@delisavas.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Cc: "solr-user@lucene.apache.org" X-Mailer: iPhone Mail (10B350) From: Erik Hatcher Subject: Re: Local Solr and Webserver-Solr act differently ("and" treated like "or") Date: Wed, 16 Oct 2013 06:27:54 -0400 To: "solr-user@lucene.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org What does the debug output say from debugQuery=3Dtrue say between the two? On Oct 16, 2013, at 5:16, Stavros Delisavas wrote: > Hello Solr-Experts, >=20 > I am currently having a strange issue with my solr querys. I am running > a small php/mysql-website that uses Solr for faster text-searches in > name-lists, movie-titles, etc. Recently I noticed that the results on my > local development-environment differ from those on my webserver. Both > use the 100% same mysql-database with identical solr-queries for > data-import. > This is a sample query: >=20 > http://localhost:8080/solr/select/?q=3Dtitle%3A%28into+AND+the+AND+wild*%2= 9&version=3D2.2&start=3D0&rows=3D1000&indent=3Don&fl=3Dtitleid >=20 > It is autogenerated by an php-script and 100% identical on local and on > my webserver. My local solr gives me the expected results: all entries > that have the words "into" AND "the" AND "wild*" in them. > But my webserver acts as if I was looking for "into" OR "the" OR > "wild*", eventhough the query is the same (as shown above). That's why I > get useless (too many) results on the webserver-side. >=20 > I don't know what could be the issue. I have tried to check the > config-files but I don't really know what to look for, so it is > overwhelming for me to search through this big file without knowing. >=20 > What could be the problem, where can I check/find it and how can I solve > that problem? >=20 > In case, additional informations are needed, let me know please. >=20 > Thank you! >=20 > (Excuse my poor english, please. It's not my mother-language.)