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

spatial pointsOnly flag shouldn't force predicate to Intersects

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1
    • Component/s: modules/spatial
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      In the process of testing the pointsOnly flag, I realized RPT's optimization to force the predicate to Intersects from Within|Contains isn't sound. In the case of Within, this is only valid if there is one point per document but not multiple (since all points on a doc need to intersect the query shape), and for Contains it was simply wrong.

      Note that the strategy has no multi-valued hint or some-such. If it did, then if !multiValued && pointsOnly, then Within could be changed to Intersects. Regardless, swapping the predicate can be done at a higher level (Solr/ES).

        Attachments

          Activity

            People

            • Assignee:
              dsmiley David Smiley
              Reporter:
              dsmiley David Smiley
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: