Apache Solr Reference Guide Covering Apache Solr 6.0

UTC:
http://localhost:8983/solr/my_collection/select?q=*:*&facet.range=my_date_field&face
t=true&facet.range.start=NOW/MONTH&facet.range.end=NOW/MONTH%2B1MONTH&facet.range.ga
p=%2B1DAY
0
0
0
0
0
0
0
...
While in this example, the "days" will be computed relative to the specified time zone - including any applicable
Daylight Savings Time adjustments:
http://localhost:8983/solr/my_collection/select?q=*:*&facet.range=my_date_field&face
t=true&facet.range.start=NOW/MONTH&facet.range.end=NOW/MONTH%2B1MONTH&facet.range.ga
p=%2B1DAY&TZ=America/Los_Angeles
0
0
0
0
0
0
0
...
More DateRangeField Details
DateRangeField is almost a drop-in replacement for places where TrieDateField is used. The only
difference is that Solr's XML or SolrJ response formats will expose the stored data as a String instead of a Date.
The underlying index data for this field will be a bit larger. Queries that align to units of time a second on up
should be faster than TrieDateField, especially if it's in UTC. But the main point of DateRangeField as it's name
suggests is to allow indexing date ranges. To do that, simply supply strings in the format shown above. It also
supports specifying 3 different relational predicates between the indexed data, and the query range: Intersect
s (default), Contains, Within. You can specify the predicate by querying using the op local-params parameter
like so:
fq={!field f=dateRange op=Contains}[2013 TO 2018]
In that example, it would find documents with indexed ranges that contain (or equals) the range 2013 thru 2018.
Multi-valued overlapping indexed ranges in a document are effectively coalesced.
For a DateRangeField example use-case and possibly other information, see Solr's community wiki.
Working with Enum Fields
Apache Solr Reference Guide 6.0
59