[LUCENE-2152] Abstract Spatial distance filtering process and supported field formats

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.1
• Component/s: modules/spatial
• Lucene Fields: New
• Assignee: Chris Male
• Reporter: Chris Male
• Created: 11/Dec/09 15:07
• Updated: 28/Aug/22 12:16
• Resolved: 01/Dec/10 09:52

Description

Currently the second stage of the filtering process in the spatial contrib involves calculating the exact distance for the remaining documents, and filtering out those that fall out of the search radius. Currently this is done through the 2 impls of DistanceFilter, LatLngDistanceFilter and GeoHashDistanceFilter. The main difference between these 2 impls is the format of data they support, the former supporting lat/lngs being stored in 2 distinct fields, while the latter supports geohashed lat/lngs through the GeoHashUtils. This difference should be abstracted out so that the distance filtering process is data format agnostic.

The second issue is that the distance filtering algorithm can be considerably optimized by using multiple-threads. Therefore it makes sense to have an abstraction of DistanceFilter which has different implementations, one being a multi-threaded implementation and the other being a blank implementation that can be used when no distance filtering is to occur.

Issue Links

• incorporates: LUCENE-1732 Multi-threaded Spatial Search
• is depended upon by: LUCENE-2395 Add a scoring DistanceQuery that does not need caches and separate filters
• is depended upon by: LUCENE-2139 Cleanup and Improvement of Spatial Contrib
• is part of: LUCENE-2350 Refactor/Cleanup Lucene Spatial