You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "There is not a rollup job that has a [date_histogram] agg on field [order_date] which also satisfies all requirements of query."
}
],
"type": "illegal_argument_exception",
"reason": "There is not a rollup job that has a [date_histogram] agg on field [order_date] which also satisfies all requirements of query."
},
"status": 400
}
The text was updated successfully, but these errors were encountered:
Right, I see the issue. The timezone in use here (Canada/Mountain) and in the discuss issue (Japan) are "obsolete" timezones and have been replaced by America/Edmonton / Asia/Tokyo respectively.
What's happening is that internally the date_histogram is converting the TZ on the fly to the "new" timezone, but rollup is comparing it against the original. So it's seeing America/Edmonton != Canada/Mountain and failing to run the query because the timezones don't match.
I think this is fixable in a bwc manner, will work on a PR.
polyfractal
changed the title
Rollup searches based on non-UTC timezones fail
Rollup searches based on "obsolete" timezones fail
Dec 4, 2018
This originated from https://discuss.elastic.co/t/visualizing-rollup-index-with-timezone-result-in-error/159064/2. CC @polyfractal
To reproduce, follow these steps to create data, a rollup job, and a search on the rolled-up data:
The search will fail with this error:
The text was updated successfully, but these errors were encountered: