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

Filter KQL field autocomplete suggestions #81584

Closed
Tracked by #166068
micwiec opened this issue Oct 26, 2020 · 4 comments
Closed
Tracked by #166068

Filter KQL field autocomplete suggestions #81584

micwiec opened this issue Oct 26, 2020 · 4 comments
Labels
discuss enhancement New value added to drive a business result Feature:KQL KQL Icebox impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@micwiec
Copy link

micwiec commented Oct 26, 2020

Possibility to exclude fields from being autosuggested by KQL.

By example in Discovery tab or in Dashboard I would like to restrict number of autosuggested fields to avoid user confusion which field or subfield they should choose.

@majagrubic majagrubic added Feature:KQL KQL discuss enhancement New value added to drive a business result labels Nov 2, 2020
@lukasolson lukasolson changed the title Filter KQL autosuggestions Filter KQL field autocomplete suggestions Feb 21, 2023
@lukasolson lukasolson added triage_needed Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. labels Feb 21, 2023
@elasticmachine
Copy link
Contributor

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

@kertal
Copy link
Member

kertal commented Feb 27, 2023

@lukasolson @mattkime could we use data view field filters for that?

@lukasolson
Copy link
Member

could we use data view field filters for that?

Currently, the docs on the page where you configure these state the following:

Field filters can be used to exclude one or more fields when fetching a document. This happens when viewing a document in the Discover app, or with a table displaying results from a saved search in the Dashboard app. If you have documents with large or unimportant fields you may benefit from filtering those out at this lower level.

I guess we have to decide whether or not there are really two separate use cases here... To prevent the field from being fetched when fetching a document (e.g. for a very large field) or to prevent certain fields from showing up in the field selection entirely. They seem related. I'll note here that adding a field filter does not prevent it from showing up wherever there is a field selector (except in the case of Discover, since the field list is populated based on the fields inside of the document fetched).

@kertal kertal added loe:medium Medium Level of Effort impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed triage_needed labels Mar 2, 2023
@kertal kertal added the Icebox label Oct 1, 2024
@kertal
Copy link
Member

kertal commented Oct 1, 2024

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 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss enhancement New value added to drive a business result Feature:KQL KQL Icebox impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Development

No branches or pull requests

5 participants