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

CartesianPolyFilterBuilder doesn't properly account for which tiers actually exist in the index

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.9, 2.9.1, 3.0
    • 3.1, 4.0-ALPHA
    • modules/spatial
    • None
    • New

    Description

      In the CartesianShapeFilterBuilder, there is logic that determines the "best fit" tier to create the Filter against. However, it does not account for which fields actually exist in the index when doing so. For instance, if you index tiers 1 through 10, but then choose a very small radius to restrict the space to, it will likely choose a tier like 15 or 16, which of course does not exist.

      Attachments

        1. ASF.LICENSE.NOT.GRANTED--LUCENE-2184.2.patch
          3 kB
          Nicolas Helleringer
        2. LUCENE-2184.patch
          6 kB
          Grant Ingersoll

        Activity

          People

            gsingers Grant Ingersoll
            gsingers Grant Ingersoll
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: