[LUCENE-6777] Switch GeoPointTermsEnum range list to use a reusable BytesRef

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.4, 6.0
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Nick Knize
• Created: 03/Sep/15 13:34
• Updated: 28/Aug/22 14:42
• Resolved: 10/Sep/15 18:47

Description

GeoPointTermsEnum currently constructs a BytesRef for every computed range, then sorts on this BytesRef. This adds an unnecessary memory overhead since the TermsEnum only requires BytesRef on calls to nextSeekTerm and accept and the ranges only need to be sorted by their long representation. This issue adds the following two improvements:

1. Lazily compute the BytesRef on demand only when its needed
2. Add a single, transient BytesRef to GeoPointTermsEnum

This will further cut back on heap usage when constructing ranges across every segment.

Issue Links

• is depended upon by: LUCENE-6780 GeoPointDistanceQuery doesn't work with a large radius?