[jira] [Updated] (SOLR-6103) Add DateRangeField

["Varun Thacker (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Varun Thacker updated SOLR-6103:
--------------------------------

    Attachment: SOLR-6103_more_tests.patch

Thanks David for clearing it out my doubts.

I added a patch which adds tests around 'dateRange' having multiple ranges. 
For this I made 'dateRange' field multiValued in the solrconfig. 

> 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, SOLR-6103_more_tests.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