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

Can we separate "top scorer" from "sub scorer"?

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.8, 6.0
    • Component/s: core/search
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      This is just an exploratory patch ... still many nocommits, but I
      think it may be promising.

      I find the two booleans we pass to Weight.scorer confusing, because
      they really only apply to whoever will call score(Collector) (just
      IndexSearcher and BooleanScorer).

      The params are pointless for the vast majority of scorers, because
      very, very few query scorers really need to change how top-scoring is
      done, and those scorers can only score top-level (throw throw UOE
      from nextDoc/advance). It seems like these two types of scorers
      should be separately typed.

        Attachments

        1. LUCENE-5487.patch
          84 kB
          Michael McCandless
        2. LUCENE-5487.patch
          86 kB
          Michael McCandless
        3. LUCENE-5487.patch
          130 kB
          Michael McCandless

          Activity

            People

            • Assignee:
              mikemccand Michael McCandless
              Reporter:
              mikemccand Michael McCandless
            • Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: