lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Resolved] (LUCENE-5579) Spatial, enhance RPT to differentiate confirmed from non-confirmed hits, then validate with SDV
Date Fri, 10 Apr 2015 19:59:15 GMT


David Smiley resolved LUCENE-5579.
       Resolution: Fixed
    Fix Version/s: 5.2
    Lucene Fields: New,Patch Available  (was: New)

> Spatial, enhance RPT to differentiate confirmed from non-confirmed hits, then validate
with SDV
> -----------------------------------------------------------------------------------------------
>                 Key: LUCENE-5579
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/spatial
>            Reporter: David Smiley
>            Assignee: David Smiley
>             Fix For: 5.2
>         Attachments: LUCENE-5579_CompositeSpatialStrategy.patch, LUCENE-5579_CompositeSpatialStrategy.patch,
LUCENE-5579_SPT_leaf_covered.patch, spatial.alg
> If a cell is within the query shape (doesn't straddle the edge), then you can be sure
that all documents it matches are a confirmed hit. But if some documents are only on the edge
cells, then those documents could be validated against SerializedDVStrategy for precise spatial
search. This should be *much* faster than using RPT and SerializedDVStrategy independently
on the same search, particularly when a lot of documents match.
> Perhaps this'll be a new RPT subclass, or maybe an optional configuration of RPT.  This
issue is just for the Intersects predicate, which will apply to Disjoint.  Until resolved
in other issues, the other predicates can be handled in a naive/slow way by creating a filter
that combines RPT's filter and SerializedDVStrategy's filter using BitsFilteredDocIdSet.
> One thing I'm not sure of is how to expose to Lucene-spatial users the underlying functionality
such that they can put other query/filters in-between RPT and the SerializedDVStrategy.  Maybe
that'll be done by simply ensuring the predicate filters have this capability and are public.
> It would be ideal to implement this capability _after_ the PrefixTree term encoding is
modified to differentiate edge leaf-cells from non-edge leaf cells. This distinction will
allow the code here to make more confirmed matches.

This message was sent by Atlassian JIRA

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

View raw message