-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
date_histogram aggregation fails for date_nanos and noon utc timezone #39107
Comments
Pinging @elastic/es-search |
@flash1293 can you look int eh ES server logs and paste the stack trace for the |
|
@jpountz @polyfractal could one of you take a look at this one? |
Pinging @elastic/es-analytics-geo |
So we were assuming that date fields only produced direct doc-value iterators, which is no longer the case with |
Hi, I am seeing a bug very similar to this pop up: elastic/kibana#40699 This query:
Is causing a failure with:
The same query without the timezone field in the date_histogram seems to work. I'm re-opening this for visibility, but if that's wrong, please offer the corrections. Thanks! |
We also had problems reviewing another PR, because also South Africa Timezone caused problems: |
@tsullivan @kertal I believe the errors mentioned in #39107 (comment) and #39107 (comment) have been resolved by #52016. Please confirm my assessment. Thank you. |
I added the YAML test in PR #85149 to confirm we don't see the issue anymore. |
When trying to apply a date_histogram aggregation with a timezone which isn't utc (tested with
Europe/Berlin
) on adate_nanos
field, elasticsearch responds with aunsupported_operation_exception
.Tested version: 7.0 snapshot
Steps to reproduce:
expected response: status code 200 and hits in the payload
actual response:
The same query with
"time_zone": "UTC",
works correctly.The text was updated successfully, but these errors were encountered: