Re: url-encoded strings from Admin Query String search

2012-03-22 Thread Aaron Couch
hi Chris and Hoss: Thanks for the feedback. This is useful to hear. This seems like a bug to me but not a very important one. I'm new to Solr and seems like you have a great community here. -Aaron On Thu, Mar 22, 2012 at 1:34 PM, Chris Hostetter wrote: > > : The admin screen is made for doing

Re: url-encoded strings from Admin Query String search

2012-03-22 Thread Chris Hostetter
: The admin screen is made for doing a quick query against the default field : with the settings defined in the default search handler. To that end, it : assumes that all entered characters should be part of the search string, so it : encodes them accordingly. correct ... that text box in questi

Re: url-encoded strings from Admin Query String search

2012-03-22 Thread fbrisbart
Maybe you don't use special characters such as '?', '&', ... in your query, but other guys do. If someone want to search for '? & the mysterians', it's impossible if you don't encode it. As the 'admin' interface must be used by anyone, the query has to be url-encoded. Franck Le mercredi 21 mars

Re: url-encoded strings from Admin Query String search

2012-03-21 Thread Shawn Heisey
On 3/21/2012 9:04 PM, Shawn Heisey wrote: The admin screen is made for doing a quick query against the default field with the settings defined in the default search handler. To that end, it assumes that all entered characters should be part of the search string, so it encodes them accordingly.

Re: url-encoded strings from Admin Query String search

2012-03-21 Thread Shawn Heisey
On 3/21/2012 5:41 PM, Aaron Couch wrote: select/?q=t_title%3Aweb%26defType%3Dlucene The '&' and '%26' are not equivalent as well as the '=' and '%3D'. I know I could easily just type the queries correctly in the URL, but I'm giving a training where I'd like to show how the queries generated in

Re: url-encoded strings from Admin Query String search

2012-03-21 Thread Aaron Couch
Thanks again for the follow-up. You are correct that '%3A' and ':' are equivalent. However if I type anything else, for example if I want to change the query parser to Lucene, the responseHeader returns an empty set. If I type in the /admin screen: t_FIELD_NAME:TEST&defType=lucene I get: selec

Re: url-encoded strings from Admin Query String search

2012-03-21 Thread fbrisbart
I'm not sure to understand your problem. The 2 urls : .../select/?q=t_FIELD_NAME%3ATEST and .../select/?q=t_FIELD_NAME:TEST are strictly the same. Look in the 'responseHeader', you'll see that query received is t_FIELD_NAME:TEST for both urls. Franck Le mercredi 21 mars 2012 à 12:36 -0500, Aa

Re: url-encoded strings from Admin Query String search

2012-03-21 Thread Aaron Couch
hi Franck; Thank you for your response. I'm not sure you understand my issue however. I have dismax on by default so am able to use query fields. My problem is not in the queries themselves, but when they are input from the '/admin' screen they are url-encoded. If I take your suggestion and type

Re: url-encoded strings from Admin Query String search

2012-03-21 Thread fbrisbart
Hi, for your example query 'TEST&qf=t_FIELD_NAME ', you can simply query : t_FIELD_NAME:TEST If you really want to use the 'qf' parameter, it is only available for dismax queries ( http://wiki.apache.org/solr/DisMaxQParserPlugin ). Your query becomes: {!dismax qf=t_FIELD_NAME}TEST Have a look at