[
https://issues.apache.org/jira/browse/SOLR-14802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198654#comment-17198654
]
David Smiley commented on SOLR-14802:
-------------------------------------
Fantastic! I've reviewed the code closely and I love how you figured out that
FunctionQParser could support field names (if configured to), and then modified
the GeoDistValueSourceParser to use that. I'll run the tests then commit this
weekend. I made a slight change to the order of some methods and to import
statement order. I'm tempted to make transformFieldSources modify the list
instead of creating a new copy but it's a minor matter.
> Sorting by min of two geodist functions
> ---------------------------------------
>
> Key: SOLR-14802
> URL: https://issues.apache.org/jira/browse/SOLR-14802
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: spatial
> Reporter: Shaun Storey
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Previously using geo field with type LatLonType you could implement a query
> like
> {code:java}
> /select?q=*:*&fl=ID&fq={!geofilt}&d=50&pt=53.4721936,-2.24703&sfield=MAIN_LOCATION&sort=min(geodist(),
> geodist(ALT_LOCATION,53.4721936,-2.24703)) asc{code}
> to sort results on minium distance from multiple different locations. Moving
> the fields to advised LatLonPointSpatialField gives
> "geodist() does not support field names in its arguments when stated fields
> are solr.LatLonPointSpatialField spatial type, requires sfield param instead"
> This has been reviewed before SOLR-11601 but not for my actual actual
> use-case so it seems the choice was to just change the error message rather
> than to implement the previous functionality. Can this be re-reviewed or let
> me know if there is another way to achieve the same result.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
