You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "steve halsey (JIRA)" <ji...@apache.org> on 2008/06/06 19:47:45 UTC

[jira] Updated: (LUCENE-1300) Negative wildcard searches on MultiSearcher not eliminating correctly.

     [ https://issues.apache.org/jira/browse/LUCENE-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

steve halsey updated LUCENE-1300:
---------------------------------

    Attachment: TestMultiSearcherNegativeWildcardQueryExpansion.java

This test fails, demonstrating the existence of the negative wildcard query on MultiSearchers bug.

> Negative wildcard searches on MultiSearcher not eliminating correctly.
> ----------------------------------------------------------------------
>
>                 Key: LUCENE-1300
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1300
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>    Affects Versions: 2.3.1
>         Environment: Windows XP, cygwin.
>            Reporter: steve halsey
>            Priority: Minor
>         Attachments: TestMultiSearcherNegativeWildcardQueryExpansion.java
>
>
>  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. 
> 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 unrelease 2.3.2 and the released 2.3.1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org