lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Resolved] (LUCENE-1122) queryparser whitespace escaping and documentation?
Date Sun, 10 Mar 2013 13:27:13 GMT


Erick Erickson resolved LUCENE-1122.

    Resolution: Won't Fix

SPRING_CLEANING_2013 We can reopen if necessary.
> queryparser whitespace escaping and documentation?
> --------------------------------------------------
>                 Key: LUCENE-1122
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/queryparser, general/website
>            Reporter: Hoss Man
>            Priority: Minor
> as noted in this solr thread...
>'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?

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message