[
https://issues.apache.org/jira/browse/LUCENE-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-7126:
-----------------------------
Fix Version/s: master (7.0)
6.1
Manually correcting fixVersion per Step #S6 of LUCENE-7271
> GeoPointDistanceRangeQuery not valid for multi-valued docs
> ----------------------------------------------------------
>
> Key: LUCENE-7126
> URL: https://issues.apache.org/jira/browse/LUCENE-7126
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Blocker
> Fix For: 6.0, 6.1, master (7.0)
>
> Attachments: LUCENE-7126.patch
>
>
> This query currently takes minimum and maximum range and rewrites to a
> boolean query of two distance queries (big NOT little).
> The problem is, this rewrite is not correct if a document has multiple values
> in the field.
> Do we really need to support this query? What is the use case? Is it a relic
> of people doing things like pagination or distance faceting in a very slow
> way? We can do these things more efficiently with other mechanisms (e.g.
> distance sort for LatLonPoint works well with searchAfter, can be ported to
> geopoint).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
