-
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
[Discover] "Add Filter" treats field contents case insensitive, but does filter case sensitive #142064
Comments
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Pinging @elastic/kibana-app-services (Team:AppServicesUx) |
Thanks for reporting this! this looks like a duplicate of #49450, but looks like that was closed by mistake, so keeping this one open. The bug is coming from the UI library elastic/eui#1997. As soon as it is fixed, we can improve this in Kibana filters |
@stratoula @lukasolson |
…rs input (#149570) ## Summary Closes #142064 Allows the selection/search of values that are same but have a different case notation. ![uni](https://user-images.githubusercontent.com/17003240/214783777-3149430c-22fc-47d0-ae52-cc29a667134e.gif)
…rs input (elastic#149570) ## Summary Closes elastic#142064 Allows the selection/search of values that are same but have a different case notation. ![uni](https://user-images.githubusercontent.com/17003240/214783777-3149430c-22fc-47d0-ae52-cc29a667134e.gif)
Kibana version: 8.4.1
Elasticsearch version: 8.4.1
Server OS version: Ubuntu 22.04 LTS
Browser version: Any
Browser OS version: Any
Original install method (e.g. download page, yum, from source, etc.): Any
Describe the bug:
When you have a field that contains the same information in different case notation (Example: host.name : Node01, node01, NODE01) between different indices (happens out of the box with different integrations), and you need to set a filter for that host.name, you need to add a filter like "field: host.name, operator: is one of" in Discovery. While picking the different case sensitive options, Kibana shows all 3 values in the list of host.name contents, but as soon as you add node01 as a value, Node01 and NODE01 disappears from the list and typing it says "node01 has already been added". The resulting filter, however, is case sensitive, so NODE01 and Node01 will not be shown in the results.
This is highly inconsistent.
Steps to reproduce:
Expected behavior:
![image](https://user-images.githubusercontent.com/33121848/192752616-76895aef-81d2-4271-9dfc-386a0c9491f1.png)
If Filter UI value picker says "already picked" then the resulting filter should also be case insensitive
Screenshots (if relevant):
Errors in browser console (if relevant):
none
Provide logs and/or server output (if relevant):
not necessary
Any additional context:
This is an actual customer complaining.
The text was updated successfully, but these errors were encountered: