| Methods Summary |
|---|
| public void | close()Frees resources associated with this Searcher.
Be careful not to call this method while you are still using objects
like {@link Hits}.
|
| public org.apache.lucene.document.Document | doc(int i)Expert: Returns the stored fields of document i.
Called by {@link HitCollector} implementations.
|
| public int | docFreq(org.apache.lucene.index.Term term)Expert: Returns the number of documents containing term.
Called by search code to compute term weights.
|
| public int[] | docFreqs(org.apache.lucene.index.Term[] terms)Expert: For each term in the terms array, calculates the number of
documents containing term. Returns an array with these
document frequencies. Used to minimize number of remote calls.
|
| public org.apache.lucene.search.Explanation | explain(org.apache.lucene.search.Weight weight, int doc)Expert: low-level implementation method
Returns an Explanation that describes how doc scored against
weight.
This is intended to be used in developing Similarity implementations,
and, for good performance, should not be displayed with every hit.
Computing an explanation is as expensive as executing the query over the
entire index.
Applications should call {@link Searcher#explain(Query, int)}.
|
| public org.apache.lucene.search.Explanation | explain(org.apache.lucene.search.Query query, int doc)
|
| public int | maxDoc()Expert: Returns one greater than the largest possible document number.
Called by search code to compute term weights.
|
| public org.apache.lucene.search.Query | rewrite(org.apache.lucene.search.Query query)Expert: called to re-write queries into primitive queries.
|
| public void | search(org.apache.lucene.search.Weight weight, org.apache.lucene.search.Filter filter, org.apache.lucene.search.HitCollector results)Lower-level search API.
{@link HitCollector#collect(int,float)} is called for every non-zero
scoring document.
HitCollector-based access to remote indexes is discouraged.
Applications should only use this if they need all of the
matching documents. The high-level search API ({@link
Searcher#search(Query)}) is usually more efficient, as it skips
non-high-scoring hits.
|
| public org.apache.lucene.search.TopFieldDocs | search(org.apache.lucene.search.Weight weight, org.apache.lucene.search.Filter filter, int n, org.apache.lucene.search.Sort sort)Expert: Low-level search implementation with arbitrary sorting. Finds
the top n hits for query, applying
filter if non-null, and sorting the hits by the criteria in
sort.
Applications should usually call {@link
Searcher#search(Query,Filter,Sort)} instead.
|
| public org.apache.lucene.search.TopFieldDocs | search(org.apache.lucene.search.Query query, org.apache.lucene.search.Filter filter, int n, org.apache.lucene.search.Sort sort)Expert: Low-level search implementation.
|
| public void | search(org.apache.lucene.search.Query query, org.apache.lucene.search.Filter filter, org.apache.lucene.search.HitCollector results)Expert: Low-level search implementation.
|
| public org.apache.lucene.search.TopDocs | search(org.apache.lucene.search.Weight weight, org.apache.lucene.search.Filter filter, int n)Expert: Low-level search implementation. Finds the top n
hits for query, applying filter if non-null.
Called by {@link Hits}.
Applications should usually call {@link Searcher#search(Query)} or
{@link Searcher#search(Query,Filter)} instead.
|
| public org.apache.lucene.search.TopDocs | search(org.apache.lucene.search.Query query, org.apache.lucene.search.Filter filter, int n)Expert: Low-level search implementation.
|
