[ 
https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Willnauer updated LUCENE-1823:
------------------------------------

    Fix Version/s:     (was: 4.0)
                   4.1

moving this over to 4.1 it seems dead to me though
                
> 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: core/queryparser
>            Reporter: Michael Busch
>            Assignee: Luis Alves
>            Priority: Minor
>             Fix For: 4.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.
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to