[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060195#comment-13060195
]
Uwe Schindler commented on LUCENE-1768:
---------------------------------------
{quote}
>>>The current code always handles Date as Long (like Solr does). I am not
>>>sure, if this would always be the best idea (see e.g. Lucene In Action
>>>book). Maybe we should add a possibility to override the conversion Date <->
>>>Number at a central place to customize? One of the reasons to not support
>>>direkt DateRangeQueries was to make the representation of Dates as Numbers
>>>open to the user.
Do you mean that Date could return some other type other than LONG? Like INT?!
I could add a new parameter to NumberDateFormat that will receive
NumeridField.DataType, this way the code could parse the date to the expected
number type.
{quote}
In general, the formatting of a Date to a Number should be possible to
customize (e.g. if you only want to format the Date without the time and your
index supports only Int dates, like number of days).
bq. I talked to Phillipe about the new API, it does not look complicated. I
will try to do the change and submit a new patch by the end of this week, then
we can finally have something checked in \o/
That communication should be done in public...
> 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: core/queryparser
> Affects Versions: 2.9
> Reporter: Uwe Schindler
> Assignee: Adriano Crestani
> Labels: contrib, gsoc, gsoc2011, lucene-gsoc-11, mentor
> Fix For: 4.0
>
> Attachments: week1.patch, week2.patch, week3.patch, week4.patch,
> week5-6.patch
>
>
> 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]
