You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Nicholas Knize (JIRA)" <ji...@apache.org> on 2015/08/01 21:56:04 UTC

[jira] [Created] (LUCENE-6712) GeoPointField should cut over to DocValues for boundary filtering

Nicholas Knize created LUCENE-6712:
--------------------------------------

             Summary: GeoPointField should cut over to DocValues for boundary filtering
                 Key: LUCENE-6712
                 URL: https://issues.apache.org/jira/browse/LUCENE-6712
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Nicholas Knize


Currently GeoPointField queries only use the Terms Dictionary for ranges that fall within and on the boundary of the query shape.  For boundary ranges the full precision terms are iterated, for within ranges the postings list is used.

Instead of iterating full precision terms for boundary ranges, this enhancement cuts over to DocValues for post-filtering boundary terms. This allows us to increase precisionStep for GeoPointField thereby reducing the number of terms and the size of the index. This enhancement should also provide a boost in query performance since visiting more docs and fewer terms should be more efficient than visiting fewer docs and more terms. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org