-
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 values are not correctly parsed in queries #47423
Comments
Pinging @elastic/es-core-infra (:Core/Infra/Core) |
Possibly related to #45284? |
it reminds me of #39916 but the version is latest |
I see - that's the one #46654 |
Thanks a lot for your competent support. I'll wait for 7.5 as it's not a show-stopper for me. |
Elasticsearch version
Version: 7.4.0, Build: default/rpm/22e1767283e61a198cb4db791ea66e3f11ab9910/2019-09-27T08:36:48.569419Z, JVM: 1.8.0_222
Java version
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (IcedTea 3.13.0) (build 1.8.0_222-b10 suse-lp151.2.3.1-x86_64)
OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)
OS version
Linux herkules 4.12.14-lp151.28.13-default
Description of the problem including expected versus actual behavior:
I have defined the following field:
I can search in this field by epoch-values but by none of the other date formats like:
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: