[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015260#comment-13015260
]
Vinicius Barros commented on LUCENE-1768:
-----------------------------------------
Hi,
Thanks Uwe and Adriano,
I finally finished and submitted my proposal to this project, please, take a
look and tell me if I need to change something. My linkid is viniciusbarros
Sorry for taking so long to submit it, but just got a free time this weekend,
college stuffs are keeping me busy.
Uwe: I added to my proposal the idea of enabling the user to enter a query that
searches for a single numeric value, example, age:19.
About DateTools, I think this can be decided later, in the end it's just a
class with some format options the user may choose. Anyway, the numeric already
have a pre-defined form to format number in strings before indexing right?!
Take a look to what I have defined in my proposal, where I allow the user to
specify a Format object, which is used by the query parser to parse the string
value entered by the user to Number. Please, let me know if I am not getting
something here.
> NumericRange support for new query parser
> -----------------------------------------
>
> Key: LUCENE-1768
> URL: https://issues.apache.org/jira/browse/LUCENE-1768
> Project: Lucene - Java
> Issue Type: New Feature
> Components: QueryParser
> Affects Versions: 2.9
> Reporter: Uwe Schindler
> Assignee: Adriano Crestani
> Labels: contrib, gsoc, gsoc2011, lucene-gsoc-11, mentor
> Fix For: 4.0
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
