New SpatialStrategy abstraction that doesn't require Spatial4j [LUCENE-6492]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
This issue is about coming up with a new (or updated) SpatialStrategy abstraction. The primary goal is to remove a dependency on Spatial4j. Some SpatialStrategies will not use/require the abstractions in Spatial4j. Strategies that support more complex/interesting cases may require Spatial4j still.
---
Migrated from [LUCENE-6492](https://issues.apache.org/jira/browse/LUCENE-6492) by David Smiley (@dsmiley)
Contributor guide
Research direction
Start by locating the existing SpatialStrategy abstraction and identifying where it depends on Spatial4j. Review the spatial strategy implementations to determine which can operate without that dependency; done means a revised abstraction supports those strategies while preserving Spatial4j for more complex cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100