public class MultiCollector extends Collector
Collector which allows running a search with several
Collectors. It offers a static wrap(org.apache.lucene.search.Collector...) method which accepts a
list of collectors and wraps them with MultiCollector, while
filtering out the null null ones.| Modifier and Type | Method and Description |
|---|---|
boolean |
acceptsDocsOutOfOrder()
Return
true if this collector does not
require the matching docIDs to be delivered in int sort
order (smallest to largest) to Collector.collect(int). |
void |
collect(int doc)
Called once for every document matching a query, with the unbased document
number.
|
void |
setNextReader(AtomicReaderContext context)
Called before collecting from each
AtomicReaderContext. |
void |
setScorer(Scorer s)
Called before successive calls to
Collector.collect(int). |
static Collector |
wrap(Collector... collectors)
Wraps a list of
Collectors with a MultiCollector. |
public static Collector wrap(Collector... collectors)
Collectors with a MultiCollector. This
method works as follows:
null collectors, so they are not used
during search time.
null ),
it is returned.
MultiCollector which wraps the
non-null ones.
IllegalArgumentException - if either 0 collectors were input, or all collectors are
null.public boolean acceptsDocsOutOfOrder()
Collectortrue if this collector does not
require the matching docIDs to be delivered in int sort
order (smallest to largest) to Collector.collect(int).
Most Lucene Query implementations will visit
matching docIDs in order. However, some queries
(currently limited to certain cases of BooleanQuery) can achieve faster searching if the
Collector allows them to deliver the
docIDs out of order.
Many collectors don't mind getting docIDs out of
order, so it's important to return true
here.
acceptsDocsOutOfOrder in class Collectorpublic void collect(int doc)
throws IOException
CollectorNote: The collection of the current segment can be terminated by throwing
a CollectionTerminatedException. In this case, the last docs of the
current AtomicReaderContext will be skipped and IndexSearcher
will swallow the exception and continue collection with the next leaf.
Note: This is called in an inner search loop. For good search performance,
implementations of this method should not call IndexSearcher.doc(int) or
IndexReader.document(int) on every hit.
Doing so can slow searches by an order of magnitude or more.
collect in class CollectorIOExceptionpublic void setNextReader(AtomicReaderContext context) throws IOException
CollectorAtomicReaderContext. All doc ids in
Collector.collect(int) will correspond to IndexReaderContext.reader().
Add AtomicReaderContext.docBase to the current IndexReaderContext.reader()'s
internal document id to re-base ids in Collector.collect(int).setNextReader in class Collectorcontext - next atomic reader contextIOExceptionpublic void setScorer(Scorer s) throws IOException
CollectorCollector.collect(int). Implementations
that need the score of the current document (passed-in to
Collector.collect(int)), should save the passed-in Scorer and call
scorer.score() when needed.setScorer in class CollectorIOExceptionCopyright © 2000-2013 Apache Software Foundation. All Rights Reserved.