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 Fri, 22 Oct 2010 14:24:15 GMT


Robert Muir commented on LUCENE-1823:

Looking at the patch, its a bit difficult to review since the patch creates a whole new queryparser

This is just my opinion here:

# I think it would be good to just modify "Standard" with the improvements presented here.
I think for contrib/queryparser to succeed, we should worry less about providing exact imitations
of the core queryparser, and instead focus on trying to provide a framework and concrete implementation
that solves the problems people are facing. In other words, fix what we don't like and provide
a parser that works the way we want, and forget about exact compatibility with the core queryparser...
if someone wants its exact behavior, they can just use it.
# It would be much easier if improvements could be on separate patches rather than bundled:
For example, LUCENE-1938 was easy for me to commit because it was well-contained and covered
one single improvement/feature.

> 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