lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adriano Crestani (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1823) QueryParser with new features for Lucene 3
Date Wed, 01 Sep 2010 03:53:55 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904892#action_12904892
] 

Adriano Crestani commented on LUCENE-1823:
------------------------------------------

I agree with Michael, AttributeSource was designed for another purpose, and does not really
fit for configuration purposes.

The map idea is really good and fits well as configuration for the QP, but I would like to
restrict the key type, so the user doesn't use a String object as key. String keys may lead
to runtime errors, mainly when they are inserted inline. I would prefer to use enums as keys,
it would enforce the user to always pass the same object as key when referencing the same
configuration. It also avoids duplicated configuration keys, once each enum type has only
one instance per JVM.

If nobody complains about using a Map<Enum<?>, Object> as configuration for QP
framework, I will start working on a new patch including these changes soon.

> 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: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message