[
https://issues.apache.org/jira/browse/LUCENE-6712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-6712:
-----------------------------------
Attachment: LUCENE-6712.patch
Updated patch includes the following:
* added GeoPointTermQueryConstantScoreWrapper accidentally left out of last
patch (forgot to add the file)
* reduces precision_step to 9 to further reduce range recursion and index size
* removed some duplicate diffs from LUCENE-6704
Due Diligence Benchmarks (on 60M point test data):
index time: 454.891 ms from 633.196 ms (*28% performance gain*)
index size: 3.9G from 4.7G (*17% reduction*)
search time: 0.018 ms/query from 0.028 ms/query (*28% performance gain*)
> 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
> Attachments: 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]
