[
https://issues.apache.org/jira/browse/SOLR-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484851#comment-13484851
]
Federico Grillini commented on SOLR-3996:
-----------------------------------------
One note: with Solr 3.5 (Solr Specification Version: 3.5.0.2011.11.22.14.54.38
- Solr Implementation Version: 3.5.0 1204988) we didn't have these problems.
> Solr 4.0.0: problems with character '/' in fields names
> -------------------------------------------------------
>
> Key: SOLR-3996
> URL: https://issues.apache.org/jira/browse/SOLR-3996
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 4.0
> Environment: Solr cloud configuration
> OS Linux
> Apache tomcat 6.0.29
> solr-spec 4.0.0.2012.10.06.03.04.33
> solr-impl 4.0.0 1394950 - rmuir - 2012-10-06 03:04:33
> jvm OpenJDK 64-Bit Server VM (14.0-b16)
> Reporter: Federico Grillini
>
> Good morning,
> we have a document management system and we use solr for fulltext searches.
> Our documents have fields with the character '/' in their names - they come
> from xml documents and we use simple xpaths as fileds names.
> We have noticed some problems in queries:
> 1. the character '/' must be escaped also if it's not mentioned as a special
> character
> (http://lucene.apache.org/core/3_6_0/queryparsersyntax.html#Escaping%20Special%20Characters);
> 2. that character must not be escaped if specified in sorting rules or in
> required fields list.
> 3. in a fields list (parameter 'fl' in a query) a field with '/' in its name
> must not be the first field if you don't want to get an error.
> I think there is a bug treating this character.
> Thanks for your help.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]