[
https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654962#action_12654962
]
Michael McCandless commented on LUCENE-1483:
--------------------------------------------
{quote}
>> make a HitCollector that gathers the results into a single pqueue
>
> That's good when everything's local, but bad when things are distributed. If
> we movE RemoteSearchable to contrib (as discussed in LUCENE-1314) then this
> may not be a problem, but we might still leave hooks so that someone can
> write a search that uses a separate top-queue per remote segment.
{quote}
Good point; so this means we can't blindly do this optimization to
MultiSearcher (w/o having option to do separate queues, merged in the end).
But for IndexSearcher(Multi*Reader).search it should be safe?
> Change IndexSearcher to use MultiSearcher semantics for sorted searches
> -----------------------------------------------------------------------
>
> Key: LUCENE-1483
> URL: https://issues.apache.org/jira/browse/LUCENE-1483
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.9
> Reporter: Mark Miller
> Priority: Minor
> Attachments: LUCENE-1483.patch
>
>
> Here is a quick test patch. FieldCache for sorting is done at the individual
> IndexReader level and reloading the fieldcache on reopen can be much faster
> as only changed segments need to be reloaded.
--
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]
