lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-2690) Date Faceting or Range Faceting doesn't take timezone into account.
Date Tue, 02 Aug 2011 16:53:27 GMT


Yonik Seeley commented on SOLR-2690:

Although this probably isn't a "bug", I agree that handling timezones somehow would be nice.
We just need to think very carefully about the API so we can support it long term.

One immediate thought I had was that it would be a pain to specify the timezone everywhere.
 Even a simple range query would need to specify it twice:
my_date:["(?timeZone=America/Chicago)NOW/YEAR" TO "(?timeZone=America/Chicago)+1MONTH"]

So one possible alternative that needs more thought is a "TZ" request parameter that would
apply by default to things that are date related.

> Date Faceting or Range Faceting doesn't take timezone into account.
> -------------------------------------------------------------------
>                 Key: SOLR-2690
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 3.3
>            Reporter: David
>   Original Estimate: 3h
>  Remaining Estimate: 3h
> Timezone needs to be taken into account when doing date math. Currently it isn't. DateMathParser
instances created are always being constructed with UTC. This is a huge issue when it comes
to faceting. Depending on your timezone day-light-savings changes the length of a month. A
facet gap of +1MONTH is different depending on the timezone and the time of the year.
> I believe the issue is very simple to fix. There are three places in the code DateMathParser
is created. All three are configured with the timezone being UTC. If a user could specify
the TimeZone to pass into DateMathParser this faceting issue would be resolved.
> Though it would be nice if we could always specify the timezone DateMathParser uses (since
date math DOES depend on timezone) its really only essential that we can affect DateMathParser
the SimpleFacets uses when dealing with the gap of the date facets.
> Another solution is to expand the syntax of the expressions DateMathParser understands.
For example we could allow "(?timeZone=VALUE)" to be added anywhere within an expression.
VALUE would be the id of the timezone. When DateMathParser reads this in sets the timezone
on the Calendar it is using.
> Two examples:
> - "(?timeZone=America/Chicago)NOW/YEAR"
> - "(?timeZone=America/Chicago)+1MONTH"
> I would be more then happy to modify DateMathParser and provide a patch. I just need
a committer to agree this needs to be resolved and a decision needs to be made on the syntax
> Thanks!
> David

This message is automatically generated by JIRA.
For more information on JIRA, see:


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

View raw message