lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-1483) Change IndexSearcher to use MultiSearcher semantics for sorted searches
Date Tue, 09 Dec 2008 20:57:44 GMT


Michael McCandless commented on LUCENE-1483:

>> 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.

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:
>             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:
For additional commands, e-mail:

View raw message