lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luc Vanlerberghe (JIRA)" <j...@apache.org>
Subject [jira] Created: (LUCENE-453) Using MultiSearcher and ParallelMultiSearcher can change the sort order.
Date Wed, 12 Oct 2005 17:07:04 GMT
Using MultiSearcher and ParallelMultiSearcher can change the sort order.
------------------------------------------------------------------------

         Key: LUCENE-453
         URL: http://issues.apache.org/jira/browse/LUCENE-453
     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


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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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


Mime
View raw message