-
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
Like (~=) operator token error on 5.6.7-1.0.1 #81
Comments
I'll be focusing time this weekend on new releases and bugs, so I should be able to take a look at this then. |
@ppadovani were you able to look into this? I'm trying to make some time this week to look into this bug. |
Sorry, the port to 6.3 has taken more time than initially thought due to some of the re-org of the Kibana code... I should have 6.3 wrapped up this weekend. If you would like to look into this and submit a pull request that would be fantastic. If not, I don't see any reason why I can't knock this out this weekend as well. |
I took a quick look at this in the 6.3 release I'm working on, and it seems to be working fine. I can use this query against my test data without an issue: cars.color~="*". If you don't submit a pull request before this weekend, I should be able to look at this at your specific release level. |
Looks like a bug in the parser:
Both a filter and match_phrase but without a separating comma... not sure the match_phrase should be there... this may have been introduced by a back port of a previous fix. This shouldn't take long to resolve. |
Fixed and released. |
Ooops... I want to leave this open to verify other releases and/or fix them if I propagated this bug. |
Thanks, will try to get this verified on my end today. |
done |
Plugin version:
5.6.7-1.0.1
Kibana version:
5.6.7
Plugins installed:
nested-fields-support, x-pack
Description of the problem including expected versus actual behavior:
Using a query with the
like
operator (~=
) is failing in the Discover window, giving an error:Unexpected token { in JSON at position 25
(position changes, this particular error is from the queryhost ~= "*"
as an example).Steps to reproduce:
~=
operatorErrors in browser console (if relevant):
None
The text was updated successfully, but these errors were encountered: