lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-1823) QueryParser with new features for Lucene 3
Date Wed, 20 Oct 2010 18:28:24 GMT


Robert Muir commented on LUCENE-1823:

Adriano, I will take a look at the patch.

A few things have changed:

the LUCENE-950 issue, I changed the 
FuzzyQuery syntax to allow for foo~1 foo~2 to support exact edit distances... 
so I don't think we need to change anything there.

Additionally we also added proper regular expression support (via Lucene core's RegexpQuery).

But i'll play with the patch, and see if i can bring it up to trunk.

As far as using a Map instead of Attributes for configuration, I think this would be a really
good step!
Are you still interested in working up a patch for this one. At the moment I think all the
scare people away from the contrib/queryparser.

> QueryParser with new features for Lucene 3
> ------------------------------------------
>                 Key: LUCENE-1823
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: QueryParser
>            Reporter: Michael Busch
>            Assignee: Luis Alves
>            Priority: Minor
>             Fix For: 4.0
>         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:
For additional commands, e-mail:

View raw message