Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1, 6.0
    • Component/s: core/query/scoring
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      CustomScoreQuery wrongly applies boost^2 instead of boost.

      It wrongly incorporates its boost into the normalization factor passed down to subquery (like booleanquery does) and also multiplies it directly in its scorer.

      The only reason the test passes today is because it compares raw score magnitudes when querynorm is on, which normalizes this away.

      Changing the test to use newSearcher() demonstrates the brokenness.

        Attachments

        1. LUCENE-4935.patch
          5 kB
          Robert Muir
        2. LUCENE-4935.patch
          3 kB
          Robert Muir

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              rcmuir Robert Muir
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: