Return GeoPointField Encoding to use full 64 bit space [LUCENE-7165]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
This was originally done in #7768 but then reverted due to issues with GeoHash encoding (which has since been removed). This issue will revert the GeoPoint encoding back to full 64 bit space which will synchronize quantization TOLERANCE between `LatLonPoint` and `GeoPointField`.
---
Migrated from [LUCENE-7165](https://issues.apache.org/jira/browse/LUCENE-7165) by Nick Knize (@nknize), updated Apr 05 2016
Attachments: [LUCENE-6996.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-7165/LUCENE-6996.patch)
Linked issues:
- #8234
Contributor guide
Research direction
The issue names GeoPointField and LatLonPoint but no source files or tests. Start by reviewing the earlier change in #7768 and the attached LUCENE-6996.patch, then compare the two fields' quantization behavior. Done means GeoPointField uses the full 64-bit space and its quantization tolerance is synchronized with LatLonPoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100