lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicholas Knize (JIRA)" <>
Subject [jira] [Updated] (LUCENE-6712) GeoPointField should cut over to DocValues for boundary filtering
Date Sat, 01 Aug 2015 20:02:04 GMT


Nicholas Knize updated LUCENE-6712:
    Attachment: LUCENE-6712.patch

Initial patch with the following changes:

* adds a GeoPointTermQueryConstantScoreWrapper for cutting over to doc values on boundary
* adds a GeoPointQueryPostFilter interface for Query specific filtering
* reduces precision_step from 6 to 8 (8 terms per point instead of 11)

Initial performance benchmarks indicate ~20% boost in query performance and ~42% smaller index.

> GeoPointField should cut over to DocValues for boundary filtering
> -----------------------------------------------------------------
>                 Key: LUCENE-6712
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Nicholas Knize
>         Attachments: 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

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

View raw message