[
https://issues.apache.org/jira/browse/LUCENE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-6712.
----------------------------------------
Resolution: Fixed
Fix Version/s: Trunk
5.3
Thanks [~nknize]!
> 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
> Fix For: 5.3, Trunk
>
> Attachments: LUCENE-6712.patch, LUCENE-6712.patch, LUCENE-6712.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
