[jira] [Commented] (SOLR-11601) geodist fails for some fields when field is in parenthesis instead of sfield param

["Amrit Sarkar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320555#comment-16320555 ] 

Amrit Sarkar commented on SOLR-11601:
-------------------------------------

[~dsmiley], Sorry I missed your update. I would like to get your consensus on should we go after supporting spatial field in geodist() or just improving the error message is sufficient for now. I can work on either.

> geodist fails for some fields when field is in parenthesis instead of sfield param
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-11601
>                 URL: https://issues.apache.org/jira/browse/SOLR-11601
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: spatial
>    Affects Versions: 6.6
>            Reporter: Clemens Wyss
>            Priority: Minor
>
> Im switching my schemas from derprecated solr.LatLonType to solr.LatLonPointSpatialField.
> Now my sortquery (which used to work with solr.LatLonType):
> *sort=geodist(b4_location__geo_si,47.36667,8.55) asc*
> raises the error
> {color:red}*"sort param could not be parsed as a query, and is not a field that exists in the index: geodist(b4_location__geo_si,47.36667,8.55)"*{color}
> Invoking sort using syntax 
> {color:#14892c}sfield=b4_location__geo_si&pt=47.36667,8.55&sort=geodist() asc
> works as expected though...{color}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org