[
https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779745#action_12779745
]
Luis Alves commented on LUCENE-1823:
------------------------------------
Operator precedence order is
{code}
ANY, ~, ^, +, -, NOT, AND, OR
{code}
For example:
{code}
a OR b AND c
{code}
will now be executed as
{code}
(a OR (b AND c))
{code}
The syntax for the ANY operator is:
{code}
( a b c d ) ANY 2
{code}
Opaque syntax is:
{code}
extensioName:field:term
extensioName:field:"phrase"
{code}
Default field:
{code}
extensioName::term
extensioName::"phrase"
{code}
In the test folder standard2 there is a Opaque implementation for regex
(contrib component),
and the syntax to use this test RegexQueryParser is, all the lunece syntax and
the above, plus:
{code}
regex:field:"regular expression"
{code}
For example:
{code}
regex::"^.[aeiou]c.*$"
{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: [email protected]
For additional commands, e-mail: [email protected]
