Lucene - Core
  1. Lucene - Core
  2. LUCENE-2597

Query scorers should not use MultiFields

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-ALPHA
    • Component/s: core/search
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      Lucene does all searching/filtering per-segment, today, but there are a number of tests that directly invoke Scorer.scorer or Filter.getDocIdSet on a composite reader.

      1. LUCENE-2597.patch
        56 kB
        Michael McCandless

        Activity

        Hide
        Michael McCandless added a comment -

        Attached patch.

        Only a few query impls were affected, but many tests were directly passing composite readers to the low level API. I added a new helper class SlowMultiReaderWrapper that one can use to wrap an existing composite reader to make it [inefficiently] pretend it's an atomic reader.

        Show
        Michael McCandless added a comment - Attached patch. Only a few query impls were affected, but many tests were directly passing composite readers to the low level API. I added a new helper class SlowMultiReaderWrapper that one can use to wrap an existing composite reader to make it [inefficiently] pretend it's an atomic reader.
        Hide
        Michael McCandless added a comment -

        Forgot to resolve this...

        Show
        Michael McCandless added a comment - Forgot to resolve this...

          People

          • Assignee:
            Michael McCandless
            Reporter:
            Michael McCandless
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development