lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Resolved] (SOLR-9085) DateRangeField is broken before the year 1582
Date Fri, 13 May 2016 14:07:12 GMT


David Smiley resolved SOLR-9085.
    Resolution: Fixed

> DateRangeField is broken before the year 1582
> ---------------------------------------------
>                 Key: SOLR-9085
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 6.0
>            Reporter: David Smiley
>            Assignee: David Smiley
>             Fix For: 6.1
>         Attachments: SOLR-9085.patch
> DateRangeField has some issues for dates before 1582 (the Gregorian Change Date), following
Solr 6.  The main problem is that it uses DateMathParser which no longer observes a GCD and
then it converts that Date to a Calendar using Calendar.setTime(date) which considers the
GCD.  We can't altogether avoid as in SOLR-9080 because DateRangePrefixTree
currently fundamentally depends on it.  However I recently learned we can simply change the
GCD like so: {{cal.setGregorianChange(new Date(Long.MIN_VALUE));}} beforehand.  DateRangeField
also calls Calendar.getTime as well, which is affected by GCD considerations.
> For users that use DateRangeField but do *not* use "Date Math" and do not have 'Z' in
their date strings then date strings are completely parsed by DateRangePrefixTree and there
should be no issue.
> DateRangePrefixTree ought to be improved a bit too (in a separate issue)... like making
the GCD configurable, and setting using SimpleDateFormatter.setCalendar it uses to format.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message