Details
-
New Feature
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
New
Description
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
Attachments
Attachments
Issue Links
- incorporates
-
LUCENE-167 [PATCH] QueryParser not handling queries containing AND and OR
- Reopened
-
LUCENE-375 fish*~ parses to PrefixQuery - should be a parse exception
- Patch Available
-
LUCENE-995 Add open ended range query syntax to QueryParser
- Closed
-
LUCENE-996 Parsing mixed inclusive/exclusive range queries
- Closed
- is blocked by
-
LUCENE-1938 Precedence query parser using the contrib/queryparser framework
- Closed
- is depended upon by
-
LUCENE-3130 Use BoostAttribute in in TokenFilters to denote Terms that QueryParser should give lower boosts
- Open
- is related to
-
LUCENE-588 Escaped wildcard character in wildcard term not handled correctly
- Closed
-
LUCENE-950 IllegalArgumentException parsing "foo~1"
- Closed
-
LUCENE-1567 New flexible query parser
- Resolved
-
LUCENE-1768 NumericRange support for new query parser
- Closed
-
LUCENE-2604 add regexpquery to queryparser
- Closed
-
LUCENE-3343 Comparison operators >,>=,<,<= and = support as RangeQuery syntax in QueryParser
- Closed
-
LUCENE-1820 WildcardQueryNode to expose the positions of the wildcard characters, for easier use in processors and builders
- Open
-
LUCENE-5205 SpanQueryParser with recursion, analysis and syntax very similar to classic QueryParser
- Resolved
-
LUCENE-2039 Regex support and beyond in JavaCC QueryParser
- Closed
-
LUCENE-1486 Wildcards, ORs etc inside Phrase queries
- Closed