-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Lens] Fix existing fields query for epoch_millis dates #119508
Conversation
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally on Safari 👍
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Kibana Machine <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Joe Reuter <[email protected]>
Co-authored-by: Kibana Machine <[email protected]>
Fixes #119445
See issues for a way to reproduce this. If the data index contains documents which use epoch_millis dates, the query fails because the time range filter doesn't specify the date format which causes it to fall back to the mapping definition. This PR makes sure the format is specified in the query.
I will add a functional test for dates in epoch_millis in general in a separate Pr