Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-9373

Allow FunctionMatchQuery to customize matchCost of TwoPhaseIterator

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 8.7
    • Component/s: modules/queries
    • Labels:
    • Lucene Fields:
      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

        Issue Links

          Activity

            People

            • Assignee:
              dsmiley David Smiley
              Reporter:
              dsmiley David Smiley

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment