[
https://issues.apache.org/jira/browse/SOLR-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796280#action_12796280
]
Ryan McKinley commented on SOLR-1568:
-------------------------------------
I'm torn on this also...
The function query syntax (and all local params really) are a bit cryptic.
When I look into it though they are really powerful, and i see an advantage to
having that level of control. (and it works in solr now)
I wonder if there is a simple way to add query rewriting that would convert:
&lat=49&long=-77&radius=10
to:
&fq={!sfilt p=49,-77 f=location dist=10}
Perhaps a RequestRewrite component?
I doubt adding something like http://tuckey.org/urlrewrite/ would work
off-the-shelf, but it could go a long way to hide the ugly innards for a simple
case like this, yet still allow the power of the function query syntax.
> Implement Spatial Filter
> ------------------------
>
> Key: SOLR-1568
> URL: https://issues.apache.org/jira/browse/SOLR-1568
> Project: Solr
> Issue Type: New Feature
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.5
>
> Attachments: CartesianTierQParserPlugin.java
>
>
> Given an index with spatial information (either as a geohash,
> SpatialTileField (see SOLR-1586) or just two lat/lon pairs), we should be
> able to pass in a filter query that takes in the field name, lat, lon and
> distance and produces an appropriate Filter (i.e. one that is aware of the
> underlying field type for use by Solr.
> The interface _could_ look like:
> {code}
> &fq={!sfilt dist=20}location:49.32,-79.0
> {code}
> or it could be:
> {code}
> &fq={!sfilt lat=49.32 lat=-79.0 f=location dist=20}
> {code}
> or:
> {code}
> &fq={!sfilt p=49.32,-79.0 f=location dist=20}
> {code}
> or:
> {code}
> &fq={!sfilt lat=49.32,-79.0 fl=lat,lon dist=20}
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
