[
https://issues.apache.org/jira/browse/LUCENE-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214138#comment-15214138
]
ASF subversion and git services commented on LUCENE-7126:
---------------------------------------------------------
Commit 9a08113a53f0f526c66e1915423fb17809871995 in lucene-solr's branch
refs/heads/master from [~rcmuir]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9a08113 ]
LUCENE-7126: GeoPointDistanceRangeQuery not valid for multi-valued docs
> 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: master, 6.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]
