You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jack Krupansky (JIRA)" <ji...@apache.org> on 2014/08/02 00:43:39 UTC
[jira] [Comment Edited] (SOLR-6103) Add DateRangeField
[ https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083031#comment-14083031 ]
Jack Krupansky edited comment on SOLR-6103 at 8/1/14 10:42 PM:
---------------------------------------------------------------
One nuance is for the end of the range - [2010 TO 2012] should expand the starting date to the beginning of that period, but expand the ending date to the end of that period (2012-12-31T23:59:59.999Z). And [2010 TO 2012} would expand the ending date to the beginning (rather than the ending) of the period (2012-01-01T00:00:00Z), with the "exclusive" flag set as well.
was (Author: jkrupan):
Once nuance is for the end of the range - [2010 TO 2012] should expand the starting date to the beginning of that period, but expand the ending date to the end of that period (2012-12-31T23:59:59.999Z). And [2010 TO 2012} would expand the ending date to the beginning (rather than the ending) of the period (2012-01-01T00:00:00Z), with the "exclusive" flag set as well.
> Add DateRangeField
> ------------------
>
> Key: SOLR-6103
> URL: https://issues.apache.org/jira/browse/SOLR-6103
> Project: Solr
> Issue Type: New Feature
> Components: spatial
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: 5.0
>
> Attachments: SOLR-6103.patch
>
>
> LUCENE-5648 introduced a date range index & search capability in the spatial module. This issue is for a corresponding Solr FieldType to be named "DateRangeField". LUCENE-5648 includes a parseCalendar(String) method that parses a superset of Solr's strict date format. It also parses partial dates (e.g.: 2014-10 has month specificity), and the trailing 'Z' is optional, and a leading +/- may be present (minus indicates BC era), and "*" means all-time. The proposed field type would use it to parse a string and also both ends of a range query, but furthermore it will also allow an arbitrary range query of the form {{<calspec> TO <calspec>}} such as:
> {noformat}2000 TO 2014-05-21T10{noformat}
> Which parses as the year 2000 thru 2014 May 21st 10am (GMT).
> I suggest this syntax because it is aligned with Lucene's range query syntax.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org