Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@www.apache.org Received: (qmail 54223 invoked from network); 9 Sep 2004 06:25:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Sep 2004 06:25:41 -0000 Received: (qmail 13370 invoked by uid 500); 9 Sep 2004 06:25:29 -0000 Delivered-To: apmail-jakarta-lucene-user-archive@jakarta.apache.org Received: (qmail 13337 invoked by uid 500); 9 Sep 2004 06:25: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 13323 invoked by uid 99); 9 Sep 2004 06:25:28 -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 [143.205.118.212] (HELO proserver2.ifit.uni-klu.ac.at) (143.205.118.212) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 08 Sep 2004 23:25:27 -0700 Received: from [143.205.118.98] ([143.205.118.98]) by proserver2.ifit.uni-klu.ac.at over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713); Thu, 9 Sep 2004 08:27:19 +0200 Message-ID: <413FF7B9.8020005@ifit.uni-klu.ac.at> Date: Thu, 09 Sep 2004 08:27:05 +0200 From: sergiu gordea User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lucene Users List Subject: Re: MultiFieldQueryParser seems broken... Fix attached. References: <04Sep8.170111pdt."58612"@synergy1.parc.xerox.com> In-Reply-To: <04Sep8.170111pdt."58612"@synergy1.parc.xerox.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 09 Sep 2004 06:27:19.0297 (UTC) FILETIME=[0EBE4F10:01C49636] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Bill, I think that more people wait for this patch of MultifieldIndexParser. It would be nice if it will be included in the next realease candidate .... All the best, Sergiu Bill Janssen wrote: >Ren�, > >Thanks for your note. > >I'd think that if a user specified a query "cutting lucene", with an >implicit AND and the default fields "title" and "author", they'd >expect to see a match in which both "cutting" and "lucene" appears. That is, > >(title:cutting OR author:cutting) AND (title:lucene OR author:lucene) > >Instead, what they'd get using the current (broken) strategy of outer >combination used by the current MultiFieldQueryParser, would be > >(title:cutting OR title:lucene) AND (author:cutting OR author:lucene) > >Note that this would match even if only "lucene" occurred in the >document, as long as it occurred both in the title field and in the >author field. Or, for that matter, it would also match "Cutting on >Cutting", by Doug Cutting :-). > > > >>http://issues.apache.org/eyebrowse/ReadMsg?listName=lucene-user@jakarta.apache.org&msgId=1798116 >> >> > >Yes, the approach there is similar. I attempted to complete the >solution and provide a working replacement for MultiFieldQueryParser. > >Bill > >--------------------------------------------------------------------- >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