-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[KQL] Support single-character wildcard #36574
Comments
Pinging @elastic/kibana-app |
Pinging @elastic/kibana-app-arch (Team:AppArch) |
+1 Also, accents are pretty common for the first letter and the use of * as a first character is specifically not recommended in ES docs (for good reasons). Example: trying to search for "élevé". Would like to use "?lev?" Now I am using "lev" but it also returns unwanted match "relevé" and is expensive to run. |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner. |
Lucene query syntax allows for single character wildcards with a
?
. There appears to be no equivalent in Kibana query language. Some users would like to have this functionality when using KQL.Note: Similar functionality is possible with an
*
in the middle of a string, but likely will return more results.customer_namer: M*t
could returnMatt
whereascustomer_namer: M?t
could only return a name with the length of 3, such asMat
The text was updated successfully, but these errors were encountered: