[
https://issues.apache.org/jira/browse/LUCENE-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-6780:
-----------------------------------
Attachment: LUCENE-6780.patch
Next iteration patch off the feature branch.
bq. OK I committed a new randomized test
The test was buggy using maxLon where it expected minLon. I also updated it to
handle the case where the circle is fully contained by the rectangle. All
beasting passed.
bq. I'm seeing very slow query execution times
I had noticed this before posting the initial patch and isolated one test that
took ~45 secs to complete. The slow times were related to recomputing the bbox
and high resolution ranges for every segment on very large distance queries.
The new patch relaxes the distance criteria for the range resolution. There
are still some boundary outliers that take ~15 seconds (instead of 60+) to
complete. I can further improve this by optimizing the
GeoPointDistanceQuery.computeBBox method... or, what are your thoughts on
computing the BBox and reusing across segments??
bq. I still think there's really a bug here I committed a failing test on the
branch
bleh...indeed!! Fixed it up.
> GeoPointDistanceQuery doesn't work with a large radius?
> -------------------------------------------------------
>
> Key: LUCENE-6780
> URL: https://issues.apache.org/jira/browse/LUCENE-6780
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Attachments: LUCENE-6780.patch, LUCENE-6780.patch, LUCENE-6780.patch,
> LUCENE-6780.patch, LUCENE-6780.patch
>
>
> I'm working on LUCENE-6698 but struggling with test failures ...
> Then I noticed that TestGeoPointQuery's test never tests on large distances,
> so I modified the test to sometimes do so (like TestBKDTree) and hit test
> failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
