[
https://issues.apache.org/jira/browse/LUCENE-7325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324039#comment-15324039
]
Adrien Grand commented on LUCENE-7325:
--------------------------------------
Is my understanding correct that there will be accuracy issues due to
quantization anyways, and the bug was just hidden before because we also
quantized the search-time values? But it had accuracy issues as well since it
was more likely to consider some lat/lon points as matching even though they
were outside of the bbox, if quantization rounded to the same values.
If yes, then I am not sure this should be a blocker. This is probably even
making things easier to reason about since the rounding is happening only once
(at index time).
> GeoPointInBBoxQuery no longer includes boundaries?
> --------------------------------------------------
>
> Key: LUCENE-7325
> URL: https://issues.apache.org/jira/browse/LUCENE-7325
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 6.1
> Reporter: Michael McCandless
> Priority: Blocker
> Attachments: LUCENE-7325.patch, LUCENE-7325.patch
>
>
> {{GeoPointInBBoxQuery}} is supposed to include boundaries, and it does in 5.x
> and 6.0, but in 6.1 something broke.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
