[ https://issues.apache.org/jira/browse/LUCENE-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022854#comment-15022854 ]
Nicholas Knize commented on LUCENE-6905: ---------------------------------------- Jenkins did catch this, eventually. Looking at the randomization it looks like the probability of producing this case is quite low. The LUCENE-6846 patch will re-enable large distances and {{testGeoRelations}} which will produce more of these edge cases. > GeoPointDistanceQuery using wrapped lon for dateline crossing query > ------------------------------------------------------------------- > > Key: LUCENE-6905 > URL: https://issues.apache.org/jira/browse/LUCENE-6905 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Nicholas Knize > Fix For: Trunk, 6.0, 5.4 > > Attachments: LUCENE-6905.patch, LUCENE-6905.patch > > > GeoPointDistanceQuery handles dateline crossing by splitting the Minimum > Bounding Rectangle (MBR) into east/west ranges and rewriting to a Boolean > SHOULD. PostFiltering is accomplished by calculating the distance from the > center point to the candidate point field. Unfortunately the center point is > wrapped such that calculating the closest point on the "circle" from an > eastern point to a western MBR provides incorrect results thus causing false > negatives in the range creation. This was caught by a jenkins failure and > reproduced in 2 places: {{GeoPointDistanceTermsEnum}} and {{TestGeoRelations}} -- 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