lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6294) Generalize how IndexSearcher parallelizes collection execution
Date Thu, 26 Feb 2015 04:45:04 GMT


David Smiley commented on LUCENE-6294:

I didn't look it over in great detail but I like it.  At first I was hoping that there might
be a Collector subclass to declare it's parallel-izability with the reduce method but then
realized it wouldn't look good since the factory method to create itself wouldn't feel right.

> Generalize how IndexSearcher parallelizes collection execution
> --------------------------------------------------------------
>                 Key: LUCENE-6294
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Trivial
>         Attachments: LUCENE-6294.patch
> IndexSearcher takes an ExecutorService that can be used to parallelize collection execution.
This is useful if you want to trade throughput for latency.
> However, this executor service will only be used if you search for top docs. In that
case, we will create one collector per slide and call TopDocs.merge in the end. If you use
search(Query, Collector), the executor service will never be used.
> But there are other collectors that could work the same way as top docs collectors, eg.
TotalHitCountCollector. And maybe also some of our users' collectors. So maybe IndexSearcher
could expose a generic way to take advantage of the executor service?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message