Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
3.1
-
None
-
None
-
New
Description
The spatial contrib shouldn't tie users to one particular way of calculating distances. Wikipedia lists multiple different formulas for the great-circle distance calculation, and there are alternatives to that as well. In a situation where many documents have the same points, it would be useful to be able to cache some calculated values as well (currently this is sort of handled in the filtering process itself).
This issue addresses this by abstracting away the distance calculator, allowing the user to provide the implementation of choice. It would then be possible to swap in different distance calculation strategies without altering the distance filtering process itself.
Attachments
Attachments
Issue Links
- is depended upon by
-
LUCENE-2395 Add a scoring DistanceQuery that does not need caches and separate filters
- Resolved
-
LUCENE-2139 Cleanup and Improvement of Spatial Contrib
- Closed
- is part of
-
LUCENE-2350 Refactor/Cleanup Lucene Spatial
- Resolved