You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2008/01/08 09:55:33 UTC

[jira] Created: (LUCENE-1122) queryparser whitespace escaping and documentation?

queryparser whitespace escaping and documentation?
--------------------------------------------------

                 Key: LUCENE-1122
                 URL: https://issues.apache.org/jira/browse/LUCENE-1122
             Project: Lucene - Java
          Issue Type: Improvement
          Components: QueryParser, Website
            Reporter: Hoss Man


as noted in this solr thread...

http://www.nabble.com/PhraseQuery-and-WildcardQuery-to14503609.html#a14503609

...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...

http://lucene.apache.org/java/docs/queryparsersyntax.html#Escaping%20Special%20Characters

...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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


[jira] Updated: (LUCENE-1122) queryparser whitespace escaping and documentation?

Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller updated LUCENE-1122:
--------------------------------

    Priority: Minor  (was: Major)

> queryparser whitespace escaping and documentation?
> --------------------------------------------------
>
>                 Key: LUCENE-1122
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1122
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: QueryParser, Website
>            Reporter: Hoss Man
>            Priority: Minor
>
> as noted in this solr thread...
> http://www.nabble.com/PhraseQuery-and-WildcardQuery-to14503609.html#a14503609
> ...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...
> http://lucene.apache.org/java/docs/queryparsersyntax.html#Escaping%20Special%20Characters
> ...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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


[jira] Commented: (LUCENE-1122) queryparser whitespace escaping and documentation?

Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646275#action_12646275 ] 

Mark Miller commented on LUCENE-1122:
-------------------------------------

Its because a term is madeup of TERM_START_CHAR + TERM_CHAR*, both of which can contain an ESCAPED_CHAR, which is an escape, '\', followed by anything. So backslash space matches ESCAPED_CHAR, and the space is eaten as part of the term rather than being used as a whitespace break.

We could change it, or it sounds like its fine to leave it. If we leave it, I guess we can doc it and close this issue. Give me your preference and I'll be happy to do it.

> queryparser whitespace escaping and documentation?
> --------------------------------------------------
>
>                 Key: LUCENE-1122
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1122
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: QueryParser, Website
>            Reporter: Hoss Man
>
> as noted in this solr thread...
> http://www.nabble.com/PhraseQuery-and-WildcardQuery-to14503609.html#a14503609
> ...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...
> http://lucene.apache.org/java/docs/queryparsersyntax.html#Escaping%20Special%20Characters
> ...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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


[jira] Commented: (LUCENE-1122) queryparser whitespace escaping and documentation?

Posted by "Steven Rowe (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556934#action_12556934 ] 

Steven Rowe commented on LUCENE-1122:
-------------------------------------

{quote}
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?
{quote}

If escape() were changed to escape spaces, a previously supported use case (escaping an entire query, consisting exclusively of terms in the default field) would no longer be supported.  In this case, the Javadocs should be changed to be very explicit about the supported use case(s).

> queryparser whitespace escaping and documentation?
> --------------------------------------------------
>
>                 Key: LUCENE-1122
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1122
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: QueryParser, Website
>            Reporter: Hoss Man
>
> as noted in this solr thread...
> http://www.nabble.com/PhraseQuery-and-WildcardQuery-to14503609.html#a14503609
> ...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...
> http://lucene.apache.org/java/docs/queryparsersyntax.html#Escaping%20Special%20Characters
> ...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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org