Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@www.apache.org Received: (qmail 99831 invoked from network); 15 Nov 2004 06:40:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Nov 2004 06:40:28 -0000 Received: (qmail 30918 invoked by uid 500); 15 Nov 2004 06:40:23 -0000 Delivered-To: apmail-jakarta-lucene-dev-archive@jakarta.apache.org Received: (qmail 30742 invoked by uid 500); 15 Nov 2004 06:40:22 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 30729 invoked by uid 99); 15 Nov 2004 06:40:22 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [216.136.173.242] (HELO web12705.mail.yahoo.com) (216.136.173.242) by apache.org (qpsmtpd/0.28) with SMTP; Sun, 14 Nov 2004 22:40:14 -0800 Received: (qmail 39311 invoked by uid 60001); 15 Nov 2004 06:40:11 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=vUGvqqrm9FJ0nSiq3BFYUfXpgzQX7i8//QhXyKSWjCaUGi1b75kXKoIRDNtYZarNIAeTLR58hVrLxecw2QATMd3ptbGBQPIVV7w7N9JZ0Er3974QMQhkM4sSl+iv3CjIyfCpAY3b7AwjUaiVDXP/pS6/IguXkBdO2nsj5OGNHhM= ; Message-ID: <20041115064010.39309.qmail@web12705.mail.yahoo.com> Received: from [24.184.142.180] by web12705.mail.yahoo.com via HTTP; Sun, 14 Nov 2004 22:40:10 PST Date: Sun, 14 Nov 2004 22:40:10 -0800 (PST) From: Otis Gospodnetic Subject: Re: the future of MultiFieldQueryParser To: Lucene Developers List In-Reply-To: <200411131346.05233@danielnaber.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I would like that change, as I don't always like queries that MFQP creates. Otis --- Daniel Naber wrote: > Hi, > > I'd like to fix MultiFieldQueryParser so that it properly works with > AND > queries. Currently it rewrites AND queries so that all terms must > appear > in all fields, which rarely makes sense. > > Eric Jain suggested a new class that works for AND and OR queries: > http://issues.apache.org/eyebrowse/ReadMsg?listName=lucene-user@jakarta.apache.org&msgId=1798116 > > It seems that his code can just be added to the current > MultiFieldQueryParser class. The current static calls can then all be > > deprecated (once some feature like setting required/prohibited per > field > have been added to the new code). > > Does anybody see a problem with that? > > Regards > Daniel > > -- > http://www.danielnaber.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: lucene-dev-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-dev-help@jakarta.apache.org