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

Top Hits metric: add support for "text" datatypes #26850

Closed
fbaligand opened this issue Dec 8, 2018 · 4 comments
Closed

Top Hits metric: add support for "text" datatypes #26850

fbaligand opened this issue Dec 8, 2018 · 4 comments
Labels
enhancement New value added to drive a business result Feature:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change.

Comments

@fbaligand
Copy link
Contributor

Currently, when we use a Top Hits metric in a Data Table, we can reference a "keyword" field, but not a "text" field.
As Top Hits works at hit level, and not at aggregation level, this would be great to be able to choose a "text" field.

This is particularly useful for string fields with long text. Else, we have to define a "keyword" field with an important ignore_above setting.
@timroes timroes added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Dec 11, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@timroes timroes added Feature:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) enhancement New value added to drive a business result labels Dec 11, 2018
@tedder tedder mentioned this issue Apr 19, 2019
Closed
@rayafratkina rayafratkina mentioned this issue Feb 26, 2020
Closed
7 tasks
@Dosant Dosant added Team:AppServicesSv and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Feb 3, 2022
@elasticmachine
Copy link
Contributor

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

@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jun 14, 2022
@ppisljar
Copy link
Member

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

@ppisljar ppisljar closed this as not planned Won't fix, can't repro, duplicate, stale Aug 11, 2022
@fbaligand
Copy link
Contributor Author

Personally, I would love that this feature would be implemented!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result Feature:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@timroes @fbaligand @Dosant @ppisljar @elasticmachine