[ 
https://issues.apache.org/jira/browse/LUCENE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654720#action_12654720
 ] 

Luke Nezda commented on LUCENE-1471:
------------------------------------

* Simplified MultiSearcherThread 
** Pulled out result merging functionality - was serialized on hq anyway
    and made much more similar to parent merge logic (actually so similar it 
felt a little dirty)
** Made it a non-static inner class to cut down on parameters, though after 
moving merge logic, only saved searchables[] ref.
* Made fields searchables[] and starts[] final - really parent version of these 
same fields should probably just be protected final
* Fixed some javadoc typos
* Patch created against 724620 supersedes previous multisearcher.patch - all 
tests pass


> Faster MultiSearcher.search merge docs 
> ---------------------------------------
>
>                 Key: LUCENE-1471
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1471
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>    Affects Versions: 2.4
>            Reporter: Jason Rutherglen
>            Assignee: Michael McCandless
>            Priority: Minor
>         Attachments: LUCENE-1471.patch, multisearcher.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> MultiSearcher.search places sorted search results from individual searchers 
> into a PriorityQueue.  This can be made to be more optimal by taking 
> advantage of the fact that the results returned are already sorted.  
> The proposed solution places the sub-searcher results iterator into a custom 
> PriorityQueue that produces the sorted ScoreDocs.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to