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

Add support for significant text aggregation #31614

Closed
Tracked by #57708
lukasolson opened this issue Feb 20, 2019 · 6 comments
Closed
Tracked by #57708

Add support for significant text aggregation #31614

lukasolson opened this issue Feb 20, 2019 · 6 comments
Labels
enhancement New value added to drive a business result Feature:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) good first issue low hanging fruit low hanging fruit DO NOT USE. Use `good first issue` instead Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@lukasolson
Copy link
Member

Elasticsearch has a significant text aggregation (added in 6.0 I believe). We should add support for it inside all of the corresponding visualizations.

@lukasolson lukasolson added Feature:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Feb 20, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@danielyahn
Copy link

+1 it would be really nice to have for tag cloud viz

@gianluigiB
Copy link

+1 I'd like to use it in a data table or tag cloud together with a search in a dashboard.

When user selects one of the results in either visualizations, he/she would see where they occur within the analyzed text field of resulting documents displayed by the search.
This has huge value when trying root-cause analysis of issues described in the analyzed text field and characterized by the significant text aggregation.

Doing the same with significant terms aggregation on analyzed text (using also n-grams) quickly fills up fielddata, making that way unpractical.

@timroes timroes added the good first issue low hanging fruit label Oct 29, 2019
@timroes
Copy link
Contributor

timroes commented Oct 29, 2019

Same comment from here applies, since we need to ignore the non-aggregatable flag for those fields, and actually be able to filter based on the original ES type not our Kibana field type.

@markharwood
Copy link
Contributor

Another example of a user jumping through hoops to turn text into keyword fields because the tag cloud doesn't support significant_text.

@stratoula
Copy link
Contributor

Duplicate of #116421

@stratoula stratoula marked this as a duplicate of #116421 May 30, 2023
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:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) good first issue low hanging fruit low hanging fruit DO NOT USE. Use `good first issue` instead Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

8 participants