You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2020/05/16 06:29:00 UTC

[jira] [Created] (LUCENE-9373) Allow FunctionMatchQuery to customize matchCost of TwoPhaseIterator

David Smiley created LUCENE-9373:
------------------------------------

             Summary: 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


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: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org