Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Sat, 14 Apr 2012 00:27:17 +0000 (UTC)
From: "Hoss Man (Commented) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1162481301.24648.1334363237123.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <790177416.24646.1334363237038.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (LUCENE-3982) regex support in queryparser needs
 documented, and called out in CHANGES.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LUCENE-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253908#comment-13253908 ] 

Hoss Man commented on LUCENE-3982:
----------------------------------

Not: set to blocker so we don't release 4.0 with this change in syntax w/o documenting
                
> regex support in queryparser needs documented, and called out in CHANGES.txt
> ----------------------------------------------------------------------------
>
>                 Key: LUCENE-3982
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3982
>             Project: Lucene - Java
>          Issue Type: Sub-task
>          Components: core/queryparser
>            Reporter: Hoss Man
>            Priority: Blocker
>             Fix For: 4.0
>
>
> Spun off of LUCENE-2604 where everyone agreed this needed done, but no one has done it yet, and rmuir didn't want to leave the issue open...
> {quote}
> some issues were pointed out in a recent mailing list thread that definitely seem like they should be addressed before this is officially released...
> * queryparsersyntax.xml doesn't mention this feature at all -- as major new syntax is should really get it's own section with an example showing the syntax
> * queryparsersyntax.xml's section on "Escaping Special Characters" needs to mention that '/' is a special character
> Also: Given that Yury encountered some real world situations in which the new syntax caused problems with existing queries, it seems like we should definitely make a note about this possibility more promonient ... i'm not sure if it makes sense in MIGRATE.txt but at a minimum it seems like the existing CHANGES.txt entry should mention it, maybe something like...
> {noformat}
> * LUCENE-2604: Added RegexpQuery support to QueryParser. Regular expressions
>   are now directly supported by the standard queryparser using the syntax... 
>      fieldName:/expression/ OR /expression against default field/
>   Users who wish to search for literal "/" characters are advised to 
>   backslash-escape or quote those characters as needed. 
>   (Simon Willnauer, Robert Muir)
> {noformat}
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

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