[
https://issues.apache.org/jira/browse/SOLR-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069860#comment-13069860
]
Yonik Seeley commented on SOLR-2606:
------------------------------------
bq. Perhaps a test-class producting randomized (legal) field names of could be
of use for this and other tests?
Define "legal" ;-)
Lucene has no limits on fieldnames. I've long advocated sticking to java
identifiers (minus the $) as best practice for a whole bunch of reasons. Maybe
it was a mistake not enforcing it to begin with.
> 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: [email protected]
For additional commands, e-mail: [email protected]
