I noticed that a single backslash in the URL query got turned into a
backslash in the parsed query, which implies that the backslash was escaped
(improperly) by Solr:
http://localhost:8080/solr/select?q=12\:34&defType=edismax&debug=query&qf=content
<str name="parsedquery_toString">+12\:34</str>
As a workaround, enclose the term in quotes, without the escaping:
http://localhost:8080/solr/select?q="12:34"&defType=edismax&debug=query&qf=content
-- Jack Krupansky
-----Original Message-----
From: jefferyyuan
Sent: Friday, July 19, 2013 7:09 PM
To: solr-user@lucene.apache.org
Subject: Re: The way edismax parses colon seems weird
Thanks very much for the reply.
We are querying solr directly from browser:
http://localhost:8080/solr/select?q=12\:34&defType=edismax&debug=query&qf=content
<str name="rawquerystring">12\:34</str>
<str name="querystring">12\:34</str>
<str name="parsedquery">(+12\:34)/no_coord</str>
<str name="parsedquery_toString">+12\:34</str>
<str name="QParser">ExtendedDismaxQParser</str>
And seems this is not related with which (default) field I use to query.
--
View this message in context:
http://lucene.472066.n3.nabble.com/The-way-edismax-parses-colon-seems-weird-tp4079226p4079234.html
Sent from the Solr - User mailing list archive at Nabble.com.
