Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
New
Description
Lucene spatial needs a lot of work. We should clean it up and allow for people to use different distances (i.e. don't assume Haversine), etc. We should also merge the Solr and Lucene code into a single lib, where possible (starting w/ Distance Utils). Update the distance filter to allow for pluggable distance measures.
Also do things like not assume everything is in degrees (users may already store radians, for instance) and use constants for conversions/multiplications instead of division.
End goal: No more experimental status. Clean up the APIs, use the more common nomenclature for "tiers" and be consistent across Lucene and Solr.
Attachments
Issue Links
- incorporates
-
LUCENE-2148 Improve Spatial Point2D and Rectangle Classes
- Closed
-
LUCENE-2151 Abstract the distance calculation process in the Spatial contrib
- Closed
-
LUCENE-2152 Abstract Spatial distance filtering process and supported field formats
- Closed
-
LUCENE-2173 Simplify and tidy Cartesian Tier Code in Spatial
- Closed
-
LUCENE-2174 Add new SpatialFilter and DistanceFieldComparatorSource to Spatial
- Closed
-
LUCENE-2175 Deprecate remaining unused classes in Spatial
- Closed
- is blocked by
-
LUCENE-2367 CartesianPolyFilterBuilder has problems around the poles
- Resolved
-
LUCENE-1921 Absurdly large radius (miles) search fails to include entire earth
- Closed
-
LUCENE-2359 CartesianPolyFilterBuilder doesn't handle edge case around the 180 meridian
- Closed
- is related to
-
SOLR-773 Incorporate Local Lucene/Solr
- Closed