Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@www.apache.org Received: (qmail 28074 invoked from network); 13 Nov 2004 12:45:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 13 Nov 2004 12:45:57 -0000 Received: (qmail 71988 invoked by uid 500); 13 Nov 2004 12:45:56 -0000 Delivered-To: apmail-jakarta-lucene-dev-archive@jakarta.apache.org Received: (qmail 71961 invoked by uid 500); 13 Nov 2004 12:45:55 -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 71948 invoked by uid 99); 13 Nov 2004 12:45:55 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [194.25.134.18] (HELO mailout04.sul.t-online.com) (194.25.134.18) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 13 Nov 2004 04:45:51 -0800 Received: from fwd03.aul.t-online.de by mailout04.sul.t-online.com with smtp id 1CSxHm-0008Lx-06; Sat, 13 Nov 2004 13:45:46 +0100 Received: from pD9EBFB32.dip.t-dialin.net (ZkwJ64ZGre-S2l3OeUP6CKVuaWQhkRMl9fsll7+4YBLdu1l07igGwG@[217.235.251.50]) by fmrl03.sul.t-online.com with esmtp id 1CSxHf-21d9Lk0; Sat, 13 Nov 2004 13:45:39 +0100 From: Daniel Naber To: lucene-dev@jakarta.apache.org Subject: the future of MultiFieldQueryParser Date: Sat, 13 Nov 2004 13:46:05 +0100 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411131346.05233@danielnaber.de> X-ID: ZkwJ64ZGre-S2l3OeUP6CKVuaWQhkRMl9fsll7+4YBLdu1l07igGwG@t-dialin.net X-TOI-MSGID: 780baeaf-4855-4008-aa13-16c8677b52a0 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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