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.

Sign up for GitHub

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

Jump to bottom

[KQL] Support boosting #122514

Closed
Tracked by #166068
ppisljar opened this issue Jan 10, 2022 · 3 comments
Closed
Tracked by #166068

[KQL] Support boosting #122514

ppisljar opened this issue Jan 10, 2022 · 3 comments
Labels
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: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

@ppisljar
Copy link
Member

ppisljar commented Jan 10, 2022 •
edited by lukasolson
Loading

Currently, the Elasticsearch query string query supports boosting, which makes one term more relevant than another.

For example, quick^2 fox would boost the _score returned for documents that match only "quick" over documents that match only "fox". Values above 1 increase relevance while values between 0 and 1 reduce relevance.

This issue is a placeholder for adding support directly in KQL for boosting. The syntax may not remain the same, but the concept & functionality would.
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort labels Jan 10, 2022
@lukasolson lukasolson changed the title [kql] support Boosting [KQL] Support boosting Feb 22, 2022
@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. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Feb 24, 2022
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Apr 7, 2022
@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)

@kertal kertal mentioned this issue Sep 8, 2023
Open
@kertal
Copy link
Member

kertal commented Oct 25, 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 added the Icebox label Oct 25, 2023
@kertal kertal closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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: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
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kertal @ppisljar @elasticmachine @petrklapka