[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086569#comment-14086569
]
Varun Thacker commented on SOLR-6103:
-
Indeed. Just went through DateNRStrategyTest.
One use case which came to my mind - Specify recurring date ranges. Say summer
vacations every year . Then one could boost certain type of documents in that
period. Although I would wait till someone actually has a use case like this :)
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086492#comment-14086492
]
David Smiley commented on SOLR-6103:
Thanks Varun; committed now.
FYI the tests at the Lucene level are very thorough and use the randomized
testing mindset. So at the Solr level the Solr test may suggest it's not
tested well but it's not the case at all.
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086490#comment-14086490
]
ASF subversion and git services commented on SOLR-6103:
---
Commit 1615961 from [~dsmiley] in branch 'dev/trunk'
[ https://svn.apache.org/r1615961 ]
SOLR-6103: Test mult-valued DateRangeField (thanks Varun Thacker)
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086312#comment-14086312
]
David Smiley commented on SOLR-6103:
I'm glad you like it.
2000-00 is wrong because the displayed and toString January is 01, not 00.
It's true that internally 0 is used. Arguably this should throw an exception
but I suppose the current behavior is not unexpected.
\[2000 TO 2014] and \[2000-01 to 2014-12] should be equivalent. FYI there are
3 tests at multiple levels but the one that is easiest to see these things is
DateRangePrefixTreeTest.java
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086186#comment-14086186
]
Varun Thacker commented on SOLR-6103:
-
Hi David,
Cool feature!
I wanted to add some tests when the 'dateRange' field has multiple ranges but
wanted to clear out a doubt before I put up the patch -
What is the difference when I search with {noformat}[2000 TO 2014]{noformat}
instead of {noformat}[2000-00 TO 2014-12]{noformat}
I can see that the Filter query being formed for the later has NRShape
{noformat}[1999-12 TO 2014]{noformat}
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083071#comment-14083071
]
David Smiley commented on SOLR-6103:
I like that idea; it's inclusive right now but doesn't support inclusive via
'}'.
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (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 commented on SOLR-6103:
--
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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082991#comment-14082991
]
David Smiley commented on SOLR-6103:
Thanks Jack; although I feel that's a separate issue. But at least this field
*does* let you specify convenient prefixes of Solr's date syntax, and then get
the range equivalent for that unit of time.
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082978#comment-14082978
]
Jack Krupansky commented on SOLR-6103:
--
You might want to take a peek at the LucidWorks Search query parser support of
date queries. It would be so nice to have comparable date support in Solr
itself.
It includes the ability to auto-expand a simple partial date/time term into a
full range, as well as using partial date/time in explicit range queries.
See:
http://docs.lucidworks.com/display/lweug/Date+Queries
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082557#comment-14082557
]
David Smiley commented on SOLR-6103:
I am; I'm waiting to port some related API improvements once I figure out one
last issue. Have you tried the feature on 5x? It's very easy to.
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082535#comment-14082535
]
Adrien Brault commented on SOLR-6103:
-
[~dsmiley] Are you still planning to get that change into 4.x ?
It would allow us to solve a lot of problems that are way too hard to implement
without the DateRangeField.
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018418#comment-14018418
]
ASF subversion and git services commented on SOLR-6103:
---
Commit 1600557 from [~dsmiley] in branch 'dev/trunk'
[ https://svn.apache.org/r1600557 ]
SOLR-6103: DateRangeField
> 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
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018416#comment-14018416
]
ASF subversion and git services commented on SOLR-6103:
---
Commit 1600556 from [~dsmiley] in branch 'dev/trunk'
[ https://svn.apache.org/r1600556 ]
SOLR-6103: Add QParser arg to AbstractSpatialFieldType.parseSpatialArgs(). Make
getQueryFromSpatialArgs protected no private.
> 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
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017886#comment-14017886
]
Ryan McKinley commented on SOLR-6103:
-
+1
> 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
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6103) Add DateRangeField
[
https://issues.apache.org/jira/browse/SOLR-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004709#comment-14004709
]
David Smiley commented on SOLR-6103:
It just occurred to me that {noformat}* TO 2014{noformat} ought to be supported
but it doesn't work -- I'll fix that in LUCENE-5648.
Perhaps the range syntax should include matching '[' and ']'? It's only
pertinent for indexing ranges; at query time you might as well use the normal
range query syntax. One aspect I haven't considered is exclusive boundaries,
but I think it's generally a non-issue because of the rounding this field
supports.
Note that LUCENE-5648 is still only v5/trunk for the moment.
> 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
>
> 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 {{ TO }} 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
