You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Nicholas Knize (JIRA)" <ji...@apache.org> on 2015/10/28 03:13:28 UTC
[jira] [Updated] (LUCENE-6859) GeoPointInPolygonQuery occasionally
fails with incorrect ranges
[ https://issues.apache.org/jira/browse/LUCENE-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas Knize updated LUCENE-6859:
-----------------------------------
Attachment: LUCENE-6859.patch
Simple patch adds the following:
* asserts if GeoPointTermsEnum is empty
* adds missing cellContains relation to GeoPointInPolygonQuery
* moves polygon MBR computation to GeoUtils
I think this is ready - its a simple change that passed a 200 iteration beast and a nightly jenkins build on local box.
> GeoPointInPolygonQuery occasionally fails with incorrect ranges
> ---------------------------------------------------------------
>
> Key: LUCENE-6859
> URL: https://issues.apache.org/jira/browse/LUCENE-6859
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Nicholas Knize
> Attachments: LUCENE-6859.patch
>
>
> With high resolution polygons (small sizes) GeoPolygonTermsEnum occasionally fails to compute the correct number of ranges. In certain cases the TermsEnum is completely empty. This leads to incorrect query results in the form of both false positives and negatives.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org