Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
New
Description
FunctionMatchQuery internally has a TwoPhaseIterator using a constant matchCost. If it were customizable by the query, the user could control this ordering. I propose an optional matchCost via an overloaded constructor. Ideally the DoubleValues abstraction would have a matchCost but it doesn't, and even if it did, the user might just want real control over this at a query construction/parse level.
See similar LUCENE-9114
Attachments
Attachments
Issue Links
- relates to
-
LUCENE-9114 Add FunctionValues.cost
- Closed