protected class ConstantScoreQuery.ConstantWeight extends Weight
Constructor and Description |
---|
ConstantScoreQuery.ConstantWeight(IndexSearcher searcher) |
Modifier and Type | Method and Description |
---|---|
Explanation |
explain(AtomicReaderContext context,
int doc)
An explanation of the score computation for the named document.
|
Query |
getQuery()
The query that this concerns.
|
float |
getValueForNormalization()
The value for normalization of contained query clauses (e.g.
|
void |
normalize(float norm,
float topLevelBoost)
Assigns the query normalization factor and boost from parent queries to this.
|
Scorer |
scorer(AtomicReaderContext context,
boolean scoreDocsInOrder,
boolean topScorer,
Bits acceptDocs)
Returns a
Scorer which scores documents in/out-of order according
to scoreDocsInOrder . |
boolean |
scoresDocsOutOfOrder()
Returns true iff this implementation scores docs only out of order.
|
public ConstantScoreQuery.ConstantWeight(IndexSearcher searcher) throws IOException
IOException
public Query getQuery()
Weight
public float getValueForNormalization() throws IOException
Weight
getValueForNormalization
in class Weight
IOException
public void normalize(float norm, float topLevelBoost)
Weight
public Scorer scorer(AtomicReaderContext context, boolean scoreDocsInOrder, boolean topScorer, Bits acceptDocs) throws IOException
Weight
Scorer
which scores documents in/out-of order according
to scoreDocsInOrder
.
NOTE: even if scoreDocsInOrder
is false, it is
recommended to check whether the returned Scorer
indeed scores
documents out of order (i.e., call Weight.scoresDocsOutOfOrder()
), as
some Scorer
implementations will always return documents
in-order.
NOTE: null can be returned if no documents will be scored by this
query.
scorer
in class Weight
context
- the AtomicReaderContext
for which to return the Scorer
.scoreDocsInOrder
- specifies whether in-order scoring of documents is required. Note
that if set to false (i.e., out-of-order scoring is required),
this method can return whatever scoring mode it supports, as every
in-order scorer is also an out-of-order one. However, an
out-of-order scorer may not support DocIdSetIterator.nextDoc()
and/or DocIdSetIterator.advance(int)
, therefore it is recommended to
request an in-order scorer if use of these methods is required.topScorer
- if true, Scorer.score(Collector)
will be called; if false,
DocIdSetIterator.nextDoc()
and/or DocIdSetIterator.advance(int)
will
be called.acceptDocs
- Bits that represent the allowable docs to match (typically deleted docs
but possibly filtering other documents)Scorer
which scores documents in/out-of order.IOException
- if there is a low-level I/O errorpublic boolean scoresDocsOutOfOrder()
Weight
Collector
's
acceptsDocsOutOfOrder
and
Weight.scorer(AtomicReaderContext, boolean, boolean, Bits)
to
create a matching Scorer
instance for a given Collector
, or
vice versa.
NOTE: the default implementation returns false
, i.e.
the Scorer
scores documents in-order.
scoresDocsOutOfOrder
in class Weight
public Explanation explain(AtomicReaderContext context, int doc) throws IOException
Weight
explain
in class Weight
context
- the readers context to create the Explanation
for.doc
- the document's id relative to the given context's readerIOException
- if an IOException
occursCopyright © 2000-2013 Apache Software Foundation. All Rights Reserved.