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

Refactoring of FilteredTermsEnum and MultiTermQuery

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.0-ALPHA
    • 4.0-ALPHA
    • core/search
    • None
    • New, Patch Available

    Description

      FilteredTermsEnum is confusing as it is initially positioned to the first term. It should instead work like an uninitialized TermsEnum for a field before the first call to next() or seek().
      FilteredTermsEnums cannot implement seek() as eg. NRQ or Automaton are not able to support this. Seeking is also not needed for MTQ at all, so seek can just throw UOE.
      This issue changes some of the internal behaviour of MTQ and FilteredTermsEnum to allow also seeking in NRQ and Automaton (see comments below).

      Attachments

        1. LUCENE-2110.patch
          79 kB
          Uwe Schindler
        2. LUCENE-2110.patch
          78 kB
          Uwe Schindler
        3. LUCENE-2110.patch
          42 kB
          Uwe Schindler
        4. LUCENE-2110.patch
          42 kB
          Uwe Schindler
        5. LUCENE-2110.patch
          36 kB
          Uwe Schindler
        6. LUCENE-2110.patch
          35 kB
          Uwe Schindler
        7. LUCENE-2110-nextSeekTermUpd.patch
          3 kB
          Uwe Schindler

        Issue Links

          Activity

            People

              uschindler Uwe Schindler
              uschindler Uwe Schindler
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: