public class FieldScoreQuery extends ValueSourceQuery
The query matches all documents, and scores each document according to the numeric value of that field.
It is assumed, and expected, that:
Combining this query in a FunctionQuery allows much freedom in affecting document scores. Note, that with this freedom comes responsibility: it is more than likely that the default Lucene scoring is superior in quality to scoring modified as explained here. However, in some cases, and certainly for research experiments, this capability may turn useful.
When constructing this query, select the appropriate type. That type should match the data stored in the field. So in fact the "right" type should be selected before indexing. Type selection has effect on the RAM usage:
FieldScoreQuery.Type.BYTEconsumes 1 * maxDocs bytes.
FieldScoreQuery.Type.SHORTconsumes 2 * maxDocs bytes.
FieldScoreQuery.Type.INTconsumes 4 * maxDocs bytes.
FieldScoreQuery.Type.FLOATconsumes 8 * maxDocs bytes.
Caching: Values for the numeric field are loaded once and cached in memory for further use with the same IndexReader. To take advantage of this, it is extremely important to reuse index-readers or index-searchers, otherwise, for instance if for each query a new index reader is opened, large penalties would be paid for loading the field values into memory over and over again!
|Modifier and Type||Class and Description|
Type of score field, indicating how field values are interpreted/parsed.
|Constructor and Description|
Create a FieldScoreQuery - a query that scores each document as the value of the numeric input field.
createWeight, equals, extractTerms, hashCode, rewrite, toString
clone, combine, getBoost, getSimilarity, mergeBooleanQueries, setBoost, toString, weight
public FieldScoreQuery(String field, FieldScoreQuery.Type type)
type param tells how to parse the field string values into a numeric score value.
field- the numeric field to be used.
type- the type of the field: either