[
https://issues.apache.org/jira/browse/LUCENE-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898969#action_12898969
]
Graham P commented on LUCENE-2174:
----------------------------------
One unfortunate behaviour of the SpatialFilter is that AFAIK it can only be
"AND"-ed onto the query, and not "OR-ed"
We want to make a filter query along the lines of {!spatial radius=2 lat=xxx
long=yyy}*:* OR street:"foo street" -- which AFAIK is impossible, the spatial
filter applies to the whole query in an "AND" capacity.
Rationale: Foo street may be much be longer than 2 kilometers, and at this time
all we know is that the user is on "foo street". We want to filter the query
for results in a radius from where we've geolocated the user (middle of foo
street) but also include results that state textually that they are on "foo
street".
Similarly for when we've geolocated the user to a gerrymander-shaped suburb.
> Add new SpatialFilter and DistanceFieldComparatorSource to Spatial
> ------------------------------------------------------------------
>
> Key: LUCENE-2174
> URL: https://issues.apache.org/jira/browse/LUCENE-2174
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/spatial
> Affects Versions: 3.1
> Reporter: Chris Male
> Assignee: Simon Willnauer
> Attachments: LUCENE-2174.patch
>
>
> The current DistanceQueryBuilder and DistanceFieldComparatorSource in Spatial
> are based on the old filtering process, most of which has been deprecated in
> previous issues. These will be replaced by a new SpatialFilter class, which
> is a proper Lucene filter, and a new DistanceFieldComparatorSource which will
> be relocated and will use the new DistanceFilter interface.
--
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: [email protected]
For additional commands, e-mail: [email protected]
