-
Notifications
You must be signed in to change notification settings - Fork 7
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
Range filter not generating nested queries in Kibana 6.2.2 #59
Comments
Now THIS is a bug report! Many thanks for the details. I should be able to resolve most of these in the next day or so. |
Ok.. There was a major update in Kibana that happened from 5.x to 6.x, and it looks like the work I did on range filters did not make it... should be fixed in the latest 6.2.2-1.04. Please take a look if it solves the issue, please update this issue, but don't close it. I'll use this to port the fix to other releases, and close this when done. |
Wow, thanks for the quick response! I can confirm that it fixes the range filter issue :) |
Back ported to all supported 6.X+++ releases |
Ported to: 5.6.7, 5.6.8 and 5.6.9 |
done |
Plugin version:
5.6.6-1.0.2, 6.2.2-1.0.3
Kibana version:
5.6.6, 6.2.2
Plugins installed:
KNQL only
Description of the problem including expected versus actual behavior:
The test data was generated using
scripts/nested-support/genData.py
In Kibana 5.6.6, applying range filters does the right thing and produces a nested query.
In Kibana 6.2.2, applying range filters does the wrong thing and does not produce a nested query.
Kibana 5.6.6 does the right thing:


Kibana 6.2.2 does the wrong thing:


This also happens in discover.


Right thing:
Wrong thing:
While investigating this, I also found that some filters (built using the "Add a filter" UI) work only in certain versions of Kibana:
The text was updated successfully, but these errors were encountered: