[LUCENE-1768] NumericRange support for new query parser

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9
• Fix Version/s: 3.4, 4.0-ALPHA
• Component/s: core/queryparser
• Labels: contrib gsoc gsoc2011 lucene-gsoc-11 mentor
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Uwe Schindler
• Created: 30/Jul/09 08:04
• Updated: 28/Aug/22 12:04
• Resolved: 08/Sep/11 16:50

Description

It would be good to specify some type of "schema" for the query parser in future, to automatically create NumericRangeQuery for different numeric types? It would then be possible to index a numeric value (double,float,long,int) using NumericField and then the query parser knows, which type of field this is and so it correctly creates a NumericRangeQuery for strings like "[1.567..*]" or "(1.787..19.5]".

There is currently no way to extract if a field is numeric from the index, so the user will have to configure the FieldConfig objects in the ConfigHandler. But if this is done, it will not be that difficult to implement the rest.

The only difference between the current handling of RangeQuery is then the instantiation of the correct Query type and conversion of the entered numeric values (simple Number.valueOf(...) cast of the user entered numbers). Evenerything else is identical, NumericRangeQuery also supports the MTQ rewrite modes (as it is a MTQ).

Another thing is a change in Date semantics. There are some strange flags in the current parser that tells it how to handle dates.

Issue Links

• is blocked by: LUCENE-1567 New flexible query parser
• is related to: LUCENE-3338 Flexible query parser does not support open ranges and range queries with mixed inclusive and exclusive ranges
• is related to: LUCENE-3352 ParametricRangeQueryNodeProcessor support for time zones
• relates to: LUCENE-1823 QueryParser with new features for Lucene 3