[jira] [Updated] (SOLR-2606) Solr sort no longer works on field names with some punctuation in them

["Hoss Man (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man updated SOLR-2606:
---------------------------

    Affects Version/s: 3.1
              Summary: Solr sort no longer works on field names with some punctuation in them  (was: Solr sort no longer works on field names with dashes in them)

thanks for reporting this.

Another user on the mailing list reported a similar bug with 3.1 when trying to sort on a field named "scores:rails_f" (giving an error of "undefined field scores")

I'm fairly certain this is caused by the enhancements made in SOLR-1297 to add sorting on functions.  

Work was done in that issue to try and ensure that "eccentric" field names could still be used in sorts even when the parsing code was changed, but evidently some basic cases involving punctuation still slipped through the cracks.

> Solr sort no longer works on field names with some punctuation in them
> ----------------------------------------------------------------------
>
>                 Key: SOLR-2606
>                 URL: https://issues.apache.org/jira/browse/SOLR-2606
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 3.1, 3.2
>         Environment: Linux
>            Reporter: Mitsu Hadeishi
>
> We just upgraded from Solr 1.4 to 3.2. For the most part the upgrade went fine, however we discovered that sorting on field names with dashes in them is no longer working properly. For example, the following query used to work:
> http://[our solr server]/select/?q=computer&sort=static-need-binary+asc
> and now it gives this error:
>     HTTP Status 400 - undefined field static
>     type Status report
>     message undefined field static
>     description The request sent by the client was syntactically incorrect (undefined field static).
> It appears the parser for sorting has been changed so that it now tokenizes differently, and assumes field names cannot have dashes in them. However, field names clearly can have dashes in them. The exact same query which worked fine for us in 1.4 is now breaking in 3.2. Changing the sort field to use a field name that doesn't have a dash in it works just fine.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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