-
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
Date histogram fails to select new date range if date is scripted field #24891
Comments
I'd like to try to work on this issue. |
First query parameters:
Second query parameters:
For some reason, second query switched to using string representation of date, instead of timestamp. |
@thomasneirynck @cjcenizal could someone review my PR? |
I tried to update my pull request. But it seems something has changed and now scripted field filtering is broken in a new way. |
@markov00, I'd like to continue working on it. Could you please assign me to this task? |
Done! Thanks @Hohol for your efforts on this |
It seems change in this PR is conflicting with scripted date field filtering in brush_event.js file
It changed date format to string, but scripted date filtering requires timestamps. @flash1293, could you please explain, why can't we continue using timestamps here? |
Hi @Hohol This was changed because |
@flash1293, wow, it's sad. Forbidding negative timestamps and forcing us to use strings instead feels weird to me. |
Kibana version: 6.4.2
Elasticsearch version: 6.4.2
Server OS version: Windows 10 Enterprise
Browser version: Chrome
Original install method: download page
Describe the bug: If you have date histogram where date is scripted field, visualization fails when you try to select date range twice.
Steps to reproduce:
data.txt
Name: date, Language: painless, type: date, Format: default, Script:
return doc['timestamp'].value
Aggregation: Date Histogram, Field: date, Interval: Hourly. Apply changes.
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
The text was updated successfully, but these errors were encountered: