Absolute search results in widget using wrong time #2428
Closed
Comments
edmundoa
added a commit
that referenced
this issue
Jul 4, 2016
Absolute time ranges in widgets were getting converted into ES_DATE_FORMAT, which converts the time into UTC, but loses the time zone information from the string representation. As the AbsoluteRange create method parses the date time and tries to keep the time zone information, that resulted in UTC times being converted into local time. To fix the problem we avoid using ES_DATE_FORMAT, and use ISO8601 instead. Fixes #2428
joschi
added a commit
that referenced
this issue
Jul 5, 2016
Absolute time ranges in widgets were getting converted into ES_DATE_FORMAT, which converts the time into UTC, but loses the time zone information from the string representation. As the AbsoluteRange create method parses the date time and tries to keep the time zone information, that resulted in UTC times being converted into local time. To fix the problem we avoid using ES_DATE_FORMAT, and use ISO8601 instead. Fixes #2428
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
From the mailing list:
I could reproduce the issue in the current master.
Steps to reproduce the problem
2016-06-27 00:00:00
to2016-06-28 00:00:00
from=2016-06-26T22%3A00%3A00.000Z&to=2016-06-27T22%3A00%3A00.000Z
{ "from": "2016-06-26T20:00:00.000+0000", "to": "2016-06-27T20:00:00.000+0000", "type": "absolute" }
as time rangeEnvironment
The text was updated successfully, but these errors were encountered: