Kibana should set lenient=true query param #59501
Labels
enhancement
New value added to drive a business result
Feature:KQL
KQL
Feature:Search
Querying infrastructure in Kibana
Icebox
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:needs-research
This issue requires some research before it can be worked on or estimated
Team:DataDiscovery
Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
For ES indices containing non-text default fields, the Kibana ofter returns "shards failed", error "Can only use prefix queries on keyword and text fields" or similar. This is caused by default fields and users typing something like "error*" to kibana query bar. For LUCENE only syntax it is possible to include "lenient" param to query:queryString:options. For KQL it is not possible. In the ES 6 days where beats did not defined default fields for templates it was working file with _all. Now the Kibana shoud pass lenient param to make better user experience. This param is even very practical. Lets imagine we want to find string beginning with "somestr*" while the field containing this string is not known. Simply querying all fields without passing "lenient" to true causes query to fail.
The text was updated successfully, but these errors were encountered: