lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luis Alves (JIRA)" <>
Subject [jira] Commented: (LUCENE-1768) NumericRange support for new query parser
Date Fri, 07 Aug 2009 18:19:14 GMT


Luis Alves commented on LUCENE-1768:

What's the cleaner way to do this? EG could I make my own ParametricRangeQueryNodeProcessor,
subclassing the current one in the "standard.processors" package, that overrides postProcessNode
to do its own conversion?

For Yonik simple requirement, you could

Option 1 (more flexible):
- make your own ParametricRangeQueryNodeProcessor, subclassing the current, returning NumericQueryNodes
where needed
- create a NumericQueryNode that extends RangeQueryNode (node extra code needed)
- create a NumericQueryNodeBuilder  that handles NumericQueryNodes, and set the map in  StandardQueryTreeBuilder,
ex: setBuilder(NumericQueryNode.class, new NumericQueryNodeBuilder()),. RangeQueryNodes will
still be normally handled by the RangeQueryNodeBuilder.

Option 2, (less flexible):
- make your own RangeQueryNodeBuilder subclassing the current(ex: NumericQueryNodeBuilder)
, set the map in StandardQueryTreeBuilder, ex: setBuilder(RangeQueryNode.class, new NumericQueryNodeBuilder())

Option 1, implements the correct usage of the APIs. It's more flexible and "dirty work" is
done in the processors pipeline.
Option 2, is not the correct use case for the APIs, requires less code and it will work, but
the builder will be performing the tasks the Processor should be doing.

> NumericRange support for new query parser
> -----------------------------------------
>                 Key: LUCENE-1768
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: QueryParser
>    Affects Versions: 2.9
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>             Fix For: 2.9
> 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.

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