lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Updated: (LUCENE-456) Duplicate hits and missing hits in sorted search
Date Tue, 18 Oct 2005 18:43:44 GMT
     [ ]

Yonik Seeley updated LUCENE-456:

    Attachment: FieldDocSortedHitQueue_dups.txt

The problem is when docs are equal, the order is unspecified.  That in conjunction with the
fact that Hits can do multiple searches under the covers, leads to your document duplication.

Everything works fine after I apply the patch I'm attaching here, in addition to the patch
And for good measure, the patch here:

> Duplicate hits and missing hits in sorted search
> ------------------------------------------------
>          Key: LUCENE-456
>          URL:
>      Project: Lucene - Java
>         Type: Bug
>   Components: Search
>     Versions: 1.4
>  Environment: JDK 1.4.2_06, probably OS independant, testet on Solaris 8 and Win2000
>     Reporter: Martin Seitz
>     Priority: Minor
>  Attachments: FieldDocSortedHitQueue_dups.txt,,
> If using a searcher that subclasses from IndexSearcher I get different result sets (besides
the ordering of course). The problem only occurrs if the searcher is wrapped by (Parallel)MultiSearcher
and the index is not too small. The number of hits returned by un unsorted and a sorted search
are identical but the hits are referencing different documents. A closer look at the result
sets revealed that the sorted search returns duplicate hits.
> I created test cases for Lucene 1.4.3 as well as for the head release. The problem showed
up for both, the number of duplicates beeing bigger for the head realease. The test cases
are written for package There are messages describing the problem
written to the console. In order to see all those hints the asserts are commented out. So
dont't be confused if junit reports no errors. (Sorry, beeing a novice user of the bug tracker
I don't see any means to attach the test cases on this screen. Let's see.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message