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

Allow FunctionMatchQuery to customize matchCost of TwoPhaseIterator

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 8.7
    • modules/queries
    • 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

        1. LUCENE-9373.patch
          4 kB
          David Smiley
        2. LUCENE-9373.patch
          4 kB
          Maxim Glazkov

        Issue Links

          Activity

            People

              dsmiley David Smiley
              dsmiley David Smiley
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: