You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2013/01/06 16:30:12 UTC

[jira] [Commented] (SOLR-4276) Handling of string field is broken

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

Shawn Heisey commented on SOLR-4276:
------------------------------------

Solr 4.0 treats a forward slash as a special character - there's regex support now, and forward slashes are how those are delineated.  When you want a slash to be part of the query text, you have to escape it with a backslash.  If you send the following as your query, does it work?

key:conf\/socc\/AscottS09

                
> Handling of string field is broken
> ----------------------------------
>
>                 Key: SOLR-4276
>                 URL: https://issues.apache.org/jira/browse/SOLR-4276
>             Project: Solr
>          Issue Type: Bug
>          Components: Schema and Analysis, search
>    Affects Versions: 4.0
>            Reporter: Thomas Beckers
>
> We upgraded from Solr 3.6 to Solr 4.0. Unfortunately the behaviour of how to retrieve a document from the index by a unique key has apparently changed.
> In Solr 3.6 the following query retrieves a single document:
> bq. key:conf/socc/AscottS09
> But when using Solr 4.0 with the same document collection (re-indexed) an empty result list is returned. It seems that Solr 4.0 is processing/analyzing the term conf/socc/AscottS09 even though it is of type solr.StrField. The query works as expected in Solr 4.0 when the term in enclosed in quotation marks:
> bq. key:"conf/socc/AscottS09"                
> schema.xml:
> {quote}
> ...
> <fieldType name="string"  class="solr.StrField" sortMissingLast="true" mitNorms="true"/>
> ...
> <field name="key" type="string" indexed="true" stored="true" multiValued="false" required="true"/>
> ...
> {quote}
> Is this a bug or have there been any changes on how Solr processes the string field?
> The analyzer in the admin ui does it right. But when using the query field in the admin ui with enabled debug mode it shows that the term gets analyzed and tokenized:
> {quote}
> <str name="rawquerystring">key:conf/socc/AscottS09</str><str name="querystring">key:conf/socc/AscottS09</str><str name="parsedquery">+key:conf +RegexpQuery(text:/socc/) +(+text:ascotts09 +text:ascott +text:s +text:09)</str><str name="parsedquery_toString">+key:conf +text:/socc/ +(+text:ascotts09 +text:ascott +text:s +text:09)</str
> {quote}
> see also: http://stackoverflow.com/questions/13511969/solr-4-0-searching-in-string-field

--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org