lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (LUCENE-453) Using MultiSearcher and ParallelMultiSearcher can change the sort order.
Date Tue, 18 Oct 2005 20:17:44 GMT
    [ ] 

Yonik Seeley commented on LUCENE-453:

most of the other cases are guaranteed to never have null values (except for perhaps CUSTOM)?

> Using MultiSearcher and ParallelMultiSearcher can change the sort order.
> ------------------------------------------------------------------------
>          Key: LUCENE-453
>          URL:
>      Project: Lucene - Java
>         Type: Bug
>   Components: Search
>     Versions: CVS Nightly - Specify date in submission
>  Environment: Checked with revision 314961 on 2005-10-12
>     Reporter: Luc Vanlerberghe
>  Attachments: FieldDocSortedHitQueue.diff, TestSort.diff
> When using multiple sort criteria the first criterium that indicates a difference should
be used.
> When a field does not exist for a given document, special rules apply.
> From what I see in the code, it is sorted as 0 for integer and float fields, and null
Strings are sorted before others.
> This works correctly in both Lucene 1.4.3 and in trunk as long as you use a single IndexSearcher
(except perhaps in special cases, see other bug reports like LUCENE-374).
> However, in MultiSearcher and ParallelMultiSearcher, the results of the separate IndexSearchers
are merged and there an error occurs.
> The bug is located in FieldDocSortedHitQueue.
> It can even be demonstrated by passing a single indexSearcher to a MultiSearcher.
> TestCase and patch follow.

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