: The summary of your email is: client's must escape search string to prevent : Solr from failing. : : It would be a nice addition to Solr to provide a new query parameter that : tells it to treat the query text as literal text. Doing so, means you : remove the burden placed on clients to understand and escape reserved Solr : / Lucene tokens.
i'm a little lost as to what exactly you want to do here -- but i'm going to focus on your thesis statement here, and assume that you want to search on a literal piece of text and you don't want to have to worry about escaping any characters and you don't wantsolr to treat any part of the query string as special. the only way something like that works is if you only want to search a single field -- searching multiple fields, searching multiple clauses, etc... none of those types of options make sense in this context. people have already mentioned the "term" parser -- which is fine ifyou want to serach for exactly one literal term, but as a more generally solution, what people usualy want, is the "field" parser -- which works better with TextFields in general... https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-FieldQueryParser Just like the comment you've seen about the "term" parser needing an "f" localparam to specify the field, the same is true for the "field" parser. but variable refrences make this trivial to specify -- instead of using the full "{!field f=myfield}Foo Bar" syntax in your q param, you can use an alternate param ("qq" is common in many examples) for the raw data from the user... q={!field f=myfield v=$qq} & qq=whatever your usertypes https://cwiki.apache.org/confluence/display/solr/Local+Parameters+in+Queries -Hoss http://www.lucidworks.com/
