Skip to content
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

Kibana should set lenient=true query param #59501

Closed
Tracked by #166068
vbohata opened this issue Mar 6, 2020 · 4 comments
Closed
Tracked by #166068

Kibana should set lenient=true query param #59501

vbohata opened this issue Mar 6, 2020 · 4 comments
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.

Comments

@vbohata
Copy link

vbohata commented Mar 6, 2020

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.

@lukasolson lukasolson added enhancement New value added to drive a business result Feature:KQL KQL Team:AppArch labels Mar 11, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch (Team:AppArch)

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Jun 2, 2021
@exalate-issue-sync exalate-issue-sync bot removed the loe:small Small Level of Effort label May 17, 2022
@lukasolson
Copy link
Member

(Somewhat) related: #17014

@petrklapka petrklapka added Feature:Search Querying infrastructure in Kibana Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. and removed Team:AppServicesSv labels Nov 23, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@davismcphee davismcphee added the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 8, 2023
@kertal
Copy link
Member

kertal commented Oct 30, 2023

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.

@kertal kertal closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
@kertal kertal added the Icebox label Oct 30, 2023
@github-project-automation github-project-automation bot moved this to Done in current release in kibana-app-arch Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
Status: Done in current release
Development

No branches or pull requests

6 participants