lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Created] (LUCENE-6685) GeoPointInBBox/Distance queries should have safeguards
Date Sat, 18 Jul 2015 08:29:04 GMT
Michael McCandless created LUCENE-6685:

             Summary: GeoPointInBBox/Distance queries should have safeguards
                 Key: LUCENE-6685
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Michael McCandless
             Fix For: 5.3, Trunk

These queries build a big list of term ranges, where the size of the list is in proportion
to how many cells of the space filling curve are "crossed" by the perimeter of the query (I

This can easily be 100s of MBs for a big enough query ... not to mention slow to enumerate
(we still do this again for each segment).

I think the queries should have safeguards, much like we have maxDeterminizedStates for Automaton
based queries, to prevent accidental OOMEs.

But I think longer term we should either change the ranges to be enumerated on-demand and
never stored in entirety (like NumericRangeTermsEnum), or change the query so it has a fixed
budget of how many cells it's allowed to visit and then within a crossing cell it uses doc
values to post-filter.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message