Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@www.apache.org Received: (qmail 55902 invoked from network); 15 Oct 2003 15:00:42 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 15 Oct 2003 15:00:42 -0000 Received: (qmail 59894 invoked by uid 500); 15 Oct 2003 15:00:28 -0000 Delivered-To: apmail-jakarta-lucene-user-archive@jakarta.apache.org Received: (qmail 59820 invoked by uid 500); 15 Oct 2003 15:00:28 -0000 Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Users List" Reply-To: "Lucene Users List" Delivered-To: mailing list lucene-user@jakarta.apache.org Received: (qmail 59778 invoked from network); 15 Oct 2003 15:00:27 -0000 Received: from unknown (HELO c000.snv.cp.net) (209.228.32.71) by daedalus.apache.org with SMTP; 15 Oct 2003 15:00:27 -0000 Received: (cpmta 1224 invoked from network); 15 Oct 2003 08:00:29 -0700 Received: from 128.143.135.152 (HELO ehatchersolutions.com) by smtp.hatcher.net (209.228.32.71) with SMTP; 15 Oct 2003 08:00:29 -0700 X-Sent: 15 Oct 2003 15:00:29 GMT Date: Wed, 15 Oct 2003 11:00:37 -0400 Subject: Re: Dash Confusion in QueryParser - Bug? Feature? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: Lucene List To: "Lucene Users List" From: Erik Hatcher In-Reply-To: <6.0.0.22.0.20031015102033.022c2618@mail.visionstudio.com> Message-Id: <55C6613E-FF20-11D7-AEE2-000393A564E6@ehatchersolutions.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I agree that the current behavior is broken and will gladly patch it myself. I'm CC'ing lucene-dev to see if there are any objections. If there are no objections, I'll apply this patch in a couple of days. Erik On Wednesday, October 15, 2003, at 10:24 AM, Michael Giles wrote: > So how do we move this issue forward. I can't think of a single case > where a "-" with no whitespace on either side (i.e. t-shirt, Wal-Mart) > should be interpreted as a NOT command. Is there a feeling that > changing the interpretation of such cases is a break in compatibility? > I agree that it will change behavior, but I think that it will change > it for the better (i.e. fix it). The current behavior is really > broken (and very frustrating for a user trying to search). > > -Mike > > At 10:08 AM 10/15/2003, you wrote: > >> --- Ulrich Mayring wrote: >> > Victor Hadianto wrote: >> > > >> > > If the QueryParser implemented the solution that I suggested then >> > "t-shirt" >> > > will get you the correct hits :) >> > >> > Well, what's the problem? I saw a couple of +1s, so why is your >> patch >> > >> > not added? >> >> 1. +1s were from non-developers >> 2. The change looked like it would not be backwards compatible. (see >> the original email from Victor) >> >> It is also better if patches are added to Bugzilla. >> >> Otis >> >> >> __________________________________ >> Do you Yahoo!? >> The New Yahoo! Shopping - with improved product search >> http://shopping.yahoo.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org >> For additional commands, e-mail: lucene-user-help@jakarta.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: lucene-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-user-help@jakarta.apache.org