[
https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779692#action_12779692
]
Luis Alves edited comment on LUCENE-1823 at 11/18/09 10:19 PM:
---------------------------------------------------------------
This patch is the first patch to implement the features described on
lucene-1823.
contains:
- Operator precedence
- Opaque terms
- ANY operator
The new parser is name standard2, I'm open to change this name please post
suggestions :)
Also included is a implementation for regex using the syntax discussed in
LUCENE-2039. I wrote a simple junit and and RegexQueryParser in the test
folder. This implementation use the Opaque terms implementation.
was (Author: lafa):
This patch is the first patch to implement the features described on
lucene-1823.
contains:
- Operator precedence
- Opaque terms
- ANY operator
The new parser is name standard2, I'm open to change this name please post
suggestions :)
Also included is a implementation for regex, using the syntax discussed in
LUCENE-2039. I wrote a simple junit and and RegexQueryParser in the test folder.
> 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.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: [email protected]
For additional commands, e-mail: [email protected]
