[
https://issues.apache.org/jira/browse/LUCENE-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-6704:
-----------------------------------
Attachment: LUCENE-6704.patch
Patch attached with the following enhancements:
1. Leaves DETAIL_LEVEL fixed at 16 w/ GeoPointField.PRECISION_STEP fixed at 6.
2. Updates relation logic to relate candidate cells to the appropriate shape.
3. Changes mortonEncoding logic to use full 32 bits per lat/lon (full 64 bit
long precision). This fixes an accuracy bug where the max lon/lat correctly
decodes to 180,90 (instead of 179.999999, 89.999999).
Note that this patch will break the current patch for LUCENE-6647. Updated
patch for that coming next.
> GeoPointInBBox/Distance queries can throw OOME
> ----------------------------------------------
>
> Key: LUCENE-6704
> URL: https://issues.apache.org/jira/browse/LUCENE-6704
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Nicholas Knize
> Attachments: LUCENE-6704.patch
>
>
> After investigating LUCENE-6685 the performance issues and improvements
> related to GeoPointInBBox/Distance queries could be categorized into two
> separate issues:
>
> 1. OOME caused by an unnecessary number of ranges computed for Point Distance
> Queries (bug in the GeoPointTermEnum base class where the bounding box was
> used for intersections instead of the point radius)
> 2. API improvements providing configurable detail parameters.
> This issue addresses 1. LUCENE-6685 will further investigate the need for 2
> (after working 1 and correcting for unnecessary range detail, it looks like 2
> may not be needed)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
