[
https://issues.apache.org/jira/browse/LUCENE-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962286#comment-14962286
]
Michael McCandless commented on LUCENE-6780:
--------------------------------------------
Thanks [~nknize], I committed the patch, but put a nocommit on the AwaitsFix
(we plan to fix that before landing this right?).
I also found a bug in how midLat/Lon was computed, that was causing us to
almost always use shiftFactor=5 even when the bbox was smallish ... I fix that,
and also fixed the test not to do dateline crossing when small==true.
However {{ant test -Dtestcase=TestGeoPointQuery -Dtestmethod=testAllLatEqual
-Dtests.seed=0}} is still quite slow (~5.6 seconds on my fastish haswell box),
even though it's always using a small bbox ....
> 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-heap-used-hack.patch, LUCENE-6780.patch,
> 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]
