You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Grant Ingersoll (JIRA)" <ji...@apache.org> on 2010/03/29 19:29:27 UTC
[jira] Commented: (LUCENE-2184) CartesianPolyFilterBuilder doesn't
properly account for which tiers actually exist in the index
[ https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851013#action_12851013 ]
Grant Ingersoll commented on LUCENE-2184:
-----------------------------------------
Note, this bug exists for the "min" case too, that is when a distance is too large
> CartesianPolyFilterBuilder doesn't properly account for which tiers actually exist in the index
> ------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2184
> URL: https://issues.apache.org/jira/browse/LUCENE-2184
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/spatial
> Affects Versions: 2.9, 2.9.1, 3.0
> Reporter: Grant Ingersoll
>
> In the CartesianShapeFilterBuilder, there is logic that determines the "best fit" tier to create the Filter against. However, it does not account for which fields actually exist in the index when doing so. For instance, if you index tiers 1 through 10, but then choose a very small radius to restrict the space to, it will likely choose a tier like 15 or 16, which of course does not exist.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org