[
https://issues.apache.org/jira/browse/SOLR-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485286#comment-13485286
]
Jack Krupansky commented on SOLR-3996:
--------------------------------------
A couple of comments:
1. Slash introduces a regex query term in 4.0.
2. Escaping is not supported parameters such as "qf".
3. Solr 4.0 supports "pseudo fields" in the "fl" parameter. The items in the
list can be full function queries (and some other things, including "glob"
names). This syntax presumes (to some degree) that field names follow the rules
of java identifiers.
See:
http://wiki.apache.org/solr/CommonQueryParameters#fl
https://issues.apache.org/jira/browse/SOLR-2444
4. Although the Solr schema technically does accept arbitray names, including
white space and punctuation characters, users would be STRONGLY ADVISED to
stick with Java identifiers. Strict Java-like feld names are not required in
all circumstances, but as you note, there are some situations where the
particular situation may either require escaping or simply prohibit field names
which are not strict Java identifiers.
In short, Solr gives you a lot of rope to play with, but don't blame Solr if
that rope is not universally accepted for everything everywhere - and for all
time.
That said, feel free to propose specific enhancements for escaping, etc.
> 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]
