as noted in this solr thread...
...it's possible to escape a whitespace character in the value of a term or prefix query by using a backslash so that the QueryParser will not treat it as "special" (ie: won't split on it when dividing the input into chunks for analysis).
at a minimum, this should be noted here...
...but it got me wondering...
- is this a side effect of something else, or will QueryParser really respect this everywhere? even in field names? (i haven't tested) ... i think this is a result of QueryParser allowing you to escape any character even if it isn't "special" to the syntax
- shouldn't a space be considered "special" since it does trigger certain behavior? ... so shouldn't QueryParser.escape(String) escape spaces as well as the other special characters?
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Won't Fix [ 2 ]|
|Workflow||Default workflow, editable Closed status [ 12563018 ]||jira [ 12584056 ]|
|Workflow||jira [ 12420402 ]||Default workflow, editable Closed status [ 12563018 ]|
|Priority||Major [ 3 ]||Minor [ 4 ]|