Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <1095031798.1258591899838.JavaMail.jira@brutus>
Date: Thu, 19 Nov 2009 00:51:39 +0000 (UTC)
From: "Luis Alves (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Issue Comment Edited: (LUCENE-1823) QueryParser with new
 features for Lucene 3
In-Reply-To: <993998441.1250637016649.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Luis Alves edited comment on LUCENE-1823 at 11/19/09 12:50 AM:
---------------------------------------------------------------

I forgot to say that the patch, includes LUCENE-1937 and LUCENE-1938 from Adriano Crestani to enable the precedence code.

      was (Author: lafa):
    I forgot to say that the patch, include LUCENE-1937, LUCENE-1938 from Adriano Crestani to enable the precedence code.
  
> QueryParser with new features for Lucene 3
> ------------------------------------------
>
>                 Key: LUCENE-1823
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1823
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: QueryParser
>            Reporter: Michael Busch
>            Assignee: Luis Alves
>            Priority: Minor
>             Fix For: 3.1
>
>         Attachments: lucene_1823_any_opaque_precedence_fuzzybug_v2.patch, lucene_1823_foo_bug_08_26_2009.patch
>
>
> I'd like to have a new QueryParser implementation in Lucene 3.1, ideally based on the new QP framework in contrib. It should share as much code as possible with the current StandardQueryParser implementation for easy maintainability.
> Wish list (feel free to extend):
> 1. *Operator precedence*: Support operator precedence for boolean operators
> 2. *Opaque terms*: Ability to plugin an external parser for certain syntax extensions, e.g. XML query terms
> 3. *Improved RangeQuery syntax*: Use more intuitive <=, =, >= instead of [] and {}
> 4. *Support for trierange queries*: See LUCENE-1768
> 5. *Complex phrases*: See LUCENE-1486
> 6. *ANY operator*: E.g. (a b c d) ANY 3 should match if 3 of the 4 terms occur in the same document
> 7. *New syntax for Span queries*: I think the surround parser supports this?
> 8. *Escaped wildcards*: See LUCENE-588

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