lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Naber (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-732) Use DateTools instead of deprecated DateField in QueryParser
Date Wed, 29 Nov 2006 21:33:22 GMT
    [ http://issues.apache.org/jira/browse/LUCENE-732?page=comments#action_12454449 ] 
            
Daniel Naber commented on LUCENE-732:
-------------------------------------

I'm not sure if most people use DateTools already, as it has just been added in Lucene 1.9.
Maybe you could consider an option (yes, yet another option isn't nice, I know)? Otherwise
we need to properly document how to continue using DateField, i.e. by extending QueryParser
and overwriting this method I guess.


> Use DateTools instead of deprecated DateField in QueryParser
> ------------------------------------------------------------
>
>                 Key: LUCENE-732
>                 URL: http://issues.apache.org/jira/browse/LUCENE-732
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: QueryParser
>            Reporter: Michael Busch
>         Assigned To: Michael Busch
>            Priority: Minor
>         Attachments: queryparser_datetools.patch
>
>
> The QueryParser currently uses the deprecated class DateField to create RangeQueries
with date values. However, most users probably use DateTools to store date values in their
indexes, because this is the recommended way since DateField has been deprecated. In that
case RangeQueries with date values produced by the QueryParser won't work with those indexes.
> This patch replaces the use of DateField in QueryParser by DateTools. Because DateTools
can produce date values with different resolutions, this patch adds the following methods
to QueryParser:
>   /**
>    * Sets the default date resolution used by RangeQueries for fields for which no
>    * specific date resolutions has been set. Field specific resolutions can be set
>    * with {@link #setDateResolution(String, DateTools.Resolution)}.
>    *  
>    * @param dateResolution the default date resolution to set
>    */
>   public void setDateResolution(DateTools.Resolution dateResolution);
>   
>   /**
>    * Sets the date resolution used by RangeQueries for a specific field.
>    *  
>    * @param field field for which the date resolution is to be set 
>    * @param dateResolution date resolution to set
>    */
>   public void setDateResolution(String fieldName, DateTools.Resolution dateResolution);
> (I also added the corresponding getter methods).
> Now the user can set a default date resolution used for all fields or, with the second
method, field specific date resolutions.
> The initial default resolution, which is used if the user does not set a different resolution,
is DateTools.Resolution.DAY. 
> Please let me know if you think we should use a different resolution as default.
> I extended TestQueryParser to test this new feature.
> All unit tests pass.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message