[jira] Commented: (LUCENE-2184) CartesianPolyFilterBuilder doesn't properly account for which tiers actually exist in the index

["Nicolas Helleringer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932474#action_12932474 ] 

Nicolas Helleringer commented on LUCENE-2184:
---------------------------------------------

The comment is here since the early version of local lucene by Patrick O'Leary

It is still meaningfull as the spatial contrib is still under work and could break current indexes (if we change at last the Sinusoidal Projector implemtation)

> 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: 2.9.4, 3.0.3, 3.1, 4.0
>
>         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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org