[
https://issues.apache.org/jira/browse/LUCENE-7325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Knize updated LUCENE-7325:
-----------------------------------
Attachment: LUCENE-7325.patch
The attached patch fixes a bug in {{GeoPointPrefixTermsEnum}} and removes
{{GeoPointTestUtil}} from {{TestGeoPointQuery}}. On my machine the random
testing passed a couple hundred beast iterations, but Mike's simple test still
fails. So are we sure the random tests are exercising these boundary conditions
as often as we think? Or did I miss something?
Anyway, the failure is related to LUCENE-7166. Specifically, [This
change|https://github.com/apache/lucene-solr/commit/f8ea8b855e43fc0a2fa434ab8c366de810047c8f#diff-abb82bc6b100f659fad4b75e44c018cdL63]
which Robert's comment explains quite nicely. The fix (mentioned in the
comment) is to move to the stable 64 bit encoding in LUCENE-7186. But
GeoPointField will need bwc with the 62 bit encoding. If we want this for 6.1
(which I think we will need?) it should probably be labeled as a blocker.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
