[
https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Helleringer updated LUCENE-2184:
----------------------------------------
Attachment: LUCENE-2184.2.patch
My work @ LUCENE-2359 did break Grant work here :s
Here is a patch to correct this.
I put the logic into the CartesianTierPlotter instead of the
CartesianPolyFilterBuilder as there was allready code to handle Tier level
borders there.
> 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
> Assignee: Grant Ingersoll
> Fix For: 3.1
>
> Attachments: LUCENE-2184.2.patch, LUCENE-2184.patch
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
