Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 42992 invoked from network); 8 Jun 2008 11:03:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jun 2008 11:03:08 -0000 Received: (qmail 36344 invoked by uid 500); 8 Jun 2008 11:03:08 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 36291 invoked by uid 500); 8 Jun 2008 11:03:08 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Delivered-To: moderator for java-dev@lucene.apache.org Received: (qmail 44262 invoked by uid 99); 6 Jun 2008 18:11:54 -0000 X-ASF-Spam-Status: No, hits=-2.0 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shalsey@verisign.com designates 216.168.239.74 as permitted sender) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8C800.B8823218" Subject: Bug: Negative wildcard searches on MultiSearcher not eliminating correctly. Date: Fri, 6 Jun 2008 20:10:37 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Bug: Negative wildcard searches on MultiSearcher not eliminating correctly. Thread-Index: AcjIAJ8/GlHghVagTjmww4SwjUFeIw== From: "Halsey, Stephen" To: X-OriginalArrivalTime: 06 Jun 2008 18:11:20.0995 (UTC) FILETIME=[B9086730:01C8C800] X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C8C800.B8823218 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hi, =20 I think I've discovered a bug. I've opened the following issue:- =20 https://issues.apache.org/jira/browse/LUCENE-1300 =20 with a test case class and the following description:- =20 =20 If you do a search for a negative wildcard query on a MultiSearcher where one of the searchers is empty e.g. "lucene -bug*" the hits returned incorrectly include articles with words that should be eliminated, e.g. "bug" and "bugs". This is because the query expansion is done on the index with docs in and the empty ndex separately and then combined as an OR to be run on the MultiSearcher. This incorrectly lets in docs that have the excluded wildcard terms, e.g. "bug" nd bugs". This bug would also show up with two indexes full of docs, and I can send a test to show that if required, but I think this test demonstrates the bug in the implest way.=20 The attached class TestMultiSearcherNegativeWildcardQueryExpansion.java can be put in with other tests in org.apache.lucene.search and run and will fail, showing the bug exists. I have tested this bug with the currently unreleased 2.3.2 and the released 2.1 and 2.3.1 and it fails on all. With lucene-1.5-rc1 it passes (with mods to make it work with old API) see TestMultiSearcherNegativeWildcardQueryExpansionWorksWith151.java attachment. =20 Please contact me if you need any further clarification. thanks =20 Steve. =20 ------_=_NextPart_001_01C8C800.B8823218 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi,

I = think I've=20 discovered a bug. I've opened the following issue:-

https://issues= .apache.org/jira/browse/LUCENE-1300

with a = test case=20 class and the following description:-

If you do a=20 search for a negative wildcard query on a MultiSearcher where one of the = searchers is empty e.g. "lucene -bug*" the hits returned incorrectly = include=20 articles with words that should be eliminated, e.g. "bug" and "bugs". = This is=20 because the query expansion is done on the index with docs in and the = empty ndex=20 separately and then combined as an OR to be run on the = MultiSearcher.=20 This incorrectly lets in docs that have the excluded wildcard terms, = e.g. "bug"=20 nd bugs". This bug would also show up with two indexes full of docs, and = I can=20 send a test to show that if required, but I think this test demonstrates = the bug=20 in the implest way.=20

The attached class = TestMultiSearcherNegativeWildcardQueryExpansion.java can=20 be put in with other tests in org.apache.lucene.search and run and will = fail,=20 showing the bug exists.

I have tested this bug with the currently unreleased 2.3.2 and the = released=20 2.1 and 2.3.1 and it fails on all.

With lucene-1.5-rc1 it passes (with mods to make it work with old = API) see=20 TestMultiSearcherNegativeWildcardQueryExpansionWorksWith151.java=20 attachment.

Please contact me if you need any = further=20 clarification.

thanks

Steve.

------_=_NextPart_001_01C8C800.B8823218--