[LUCENE-9373] Allow FunctionMatchQuery to customize matchCost of TwoPhaseIterator

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 8.7
• Component/s: modules/queries
• Labels: newdev
• Lucene Fields: New
• Assignee: David Smiley
• Reporter: David Smiley
• Created: 16/May/20 06:28
• Updated: 28/Aug/22 16:03
• Resolved: 24/Aug/20 04:51

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

Issue Links

• relates to: LUCENE-9114 Add FunctionValues.cost