-
Notifications
You must be signed in to change notification settings - Fork 842
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
Memory table does not construct query correctly when filtering #6349
Comments
@thomheymann can you clarify the urgency level of this bug? Is it something that needs to get in before 8.6FF? |
@constancecchen Would be great to have obviously but if there's more urgent issues 8.7 would be ok too I think. |
FYI @chandlerprall |
As long as the fix doesn't touch the query syntax parsing (doesn't sound like it will), if we can get a fix merged by EOD Thursday then a quick backport for 8.6 makes sense to me (I can run that & the Kibana update). |
I think it does (or at least that would be my preferred fix, personally, and to expand this fix to all special characters that don't have EQL meaning (e.g. not throwing on PR for review: #6356 We're also getting real close to FF so I'm not totally sure we should try and squeeze this in, unless someone else wants to pick this up. |
There is an issue with the way search bar queries are constructed when filtering in EuiMemoryTable component causing bugs when e.g. usernames or tags contain special characters: elastic/kibana#143079
To fix this values that contain special characters should be wrapped in quotation marks, e.g.:
username:user@domain
should beusername:"user@domain"
insteadtag:(tag1 or tag2@tag2)
should betag:(tag1 or "tag2@tag2")
insteadThe text was updated successfully, but these errors were encountered: