[
https://issues.apache.org/jira/browse/LUCENE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved LUCENE-9373.
----------------------------------
Fix Version/s: 8.7
Resolution: Fixed
> Allow FunctionMatchQuery to customize matchCost of TwoPhaseIterator
> -------------------------------------------------------------------
>
> Key: LUCENE-9373
> URL: https://issues.apache.org/jira/browse/LUCENE-9373
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/queries
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Labels: newdev
> Fix For: 8.7
>
> Attachments: LUCENE-9373.patch, LUCENE-9373.patch
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
