Return-Path: X-Original-To: apmail-lucenenet-user-archive@www.apache.org Delivered-To: apmail-lucenenet-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4205B10A6E for ; Tue, 12 Nov 2013 06:27:01 +0000 (UTC) Received: (qmail 63430 invoked by uid 500); 12 Nov 2013 06:27:00 -0000 Delivered-To: apmail-lucenenet-user-archive@lucenenet.apache.org Received: (qmail 63402 invoked by uid 500); 12 Nov 2013 06:27:00 -0000 Mailing-List: contact user-help@lucenenet.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@lucenenet.apache.org Delivered-To: mailing list user@lucenenet.apache.org Received: (qmail 63394 invoked by uid 99); 12 Nov 2013 06:26:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Nov 2013 06:26:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anders@lybecker.com designates 209.85.128.174 as permitted sender) Received: from [209.85.128.174] (HELO mail-ve0-f174.google.com) (209.85.128.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Nov 2013 06:26:55 +0000 Received: by mail-ve0-f174.google.com with SMTP id cz12so1908025veb.33 for ; Mon, 11 Nov 2013 22:26:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=JVpmi+OF/sYk0C5Hdp0Izj0j1mrR1rW54ruimmuclgQ=; b=fSVT5a22ucGneUa4eGaypcQzZtQP2Gkg21a3bAx6JMRuiXmXXE6XiOf2QnKSG7OehF ALuTZpkk8X0xZsISRBTTRGwoi6R9XsnR76JC/677OHZ908lARhFDl6qfbeCz0ioc6Qxr tt2WFmdONvF4IXM5Et5WR/SaOYJ4S2qevr9SxMnQMIeTJhLVFnBIhaGfcYeZAg6V39iC P7oiF8OLpjH6ME5L2RSt7kYQc3mERjHUoDSb24s+H5CzyX0HviTHbde6fn70JhIsPu6s NTGB2eKwf7rybKRv46ilX0eFlU/+ye0b4c1+qKpF49ySRx8fA6tbhZvfzTqXxAXKcoOE F2MQ== X-Gm-Message-State: ALoCoQkIyHaYsUs++5OYKrmyZH20EspQu6DtBCez3ikydDR2qy1Shok15TOYuSlUmec0XneoQivv X-Received: by 10.220.186.202 with SMTP id ct10mr28085490vcb.14.1384237594738; Mon, 11 Nov 2013 22:26:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.124.210 with HTTP; Mon, 11 Nov 2013 22:26:13 -0800 (PST) In-Reply-To: <07C9F055-14DE-4956-ADBE-7B8A2B25E904@knowles.net.au> References: <07C9F055-14DE-4956-ADBE-7B8A2B25E904@knowles.net.au> From: Anders Lybecker Date: Tue, 12 Nov 2013 07:26:13 +0100 Message-ID: Subject: Re: Prohibit operator not working with phrase To: user@lucenenet.apache.org Content-Type: multipart/alternative; boundary=047d7b676fd01ea95b04eaf4ee4c X-Virus-Checked: Checked by ClamAV on apache.org --047d7b676fd01ea95b04eaf4ee4c Content-Type: text/plain; charset=ISO-8859-1 Hi, We need to know more about your archtecture and how you index and search with Lucene. Do you have code you can share? Regards, Anders Lybecker On Tue, Nov 12, 2013 at 6:45 AM, Steven Knowles wrote: > This question will highlight how much I don't know, but hoping somebody > can help me get to the bottom of a puzzle. > > I'm trying to ascertain why inclusion of, for instance: > > -"united bank" > > .. ie. a prohibit operator and phrase, not on its own but together with > some other required operators, does NOT return a document which DOES NOT > contain the phrase "united bank". > > The document which isn't returned, but should be so far as my > understanding goes, is a Word (.doc) document. I've checked for "united > bank" within metadata, but can find no trace. I have tested another phrase > and same result, ie. the problem doesn't appear to be specific to this > particular phrase. > > The document in question is definitely indexed, because it appears in all > manner of other searches. > > I know that we use Lucene in conjunction with MySQL and ASP.NET, and this > all runs on Windows Server 2008 R2 Standard. I know also that MySQL > WorkBench 5.2.44 CE is used. But to ascertain what version of Lucene is > used, I'd need some guidance on where to look. > > Is there somebody who can guide me on whether it's a known issue, whether > I need to arrange update of Lucene, whether there's some kind of setting I > need to tweak ? > > I'm sure there's info that I haven't provided which might help somebody > answer the questions, so happy to hear what info is needed. > > I'd like to understand the reason for the problem so that I can either > tailor searches accordingly, or make it work how I think it should work. > > Many thanks, Steven --047d7b676fd01ea95b04eaf4ee4c--