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

Use Terms.getMin/Max to speed up range queries/filters

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 4.10, 6.0
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      As of LUCENE-5610, Lucene's Terms API now exposes min and max terms in
      each field. I think we can use this in our term/numeric range
      query/filters to avoid visiting a given segment by detecting up front
      that the terms in the segment don't overlap with the query's range.

      Even though block tree avoids disk seeks in certain cases when the
      term cannot exist on-disk, I think this change would further avoid
      disk seeks in additional cases because the min/max term has
      more/different information than the in-memory FST terms index.

        Attachments

        1. LUCENE-5860.patch
          9 kB
          Michael McCandless

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: