-
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
[ES|QL] date_parse seems to ignore timezone #117680
Comments
Pinging @elastic/es-analytical-engine (Team:Analytics) |
Per documentation, ES|QL only supports UTC at the moment (e.g it does not support timezones) : https://www.elastic.co/guide/en/elasticsearch/reference/current/esql-limitations.html#esql-limitations-timezone |
Thank you for the answer. That's sad though :( |
Not sure if the lack of support for UTC might be it. I think parsing should read the timezone as is and then only output in UTC, b/c we support no other TZs. I'll have a look. |
This just removes fixing a formatter to a timezone (UTC), allowing `DATE_PARSE` to correctly read timezones. Fixes #117680.
This just removes fixing a formatter to a timezone (UTC), allowing `DATE_PARSE` to correctly read timezones. Fixes elastic#117680.
This just removes fixing a formatter to a timezone (UTC), allowing `DATE_PARSE` to correctly read timezones. Fixes elastic#117680.
This just removes fixing a formatter to a timezone (UTC), allowing `DATE_PARSE` to correctly read timezones. Fixes elastic#117680.
Elasticsearch Version
8.16.0
Installed Plugins
No response
Java Version
bundled
OS Version
Linux amd64 5.15.0-1032-gcp
Problem Description
produces
but
produces
I suspect
date_parse
in ES|QL ignores the timezone offset. Will you look into it, please?Steps to Reproduce
You can run
, which produces
I think
@timestamp
should be "2022-07-12T01:24:10.000Z".Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: