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

Support bucket_sort aggregation #123719

Closed
iuriikhrystiuk opened this issue Jan 25, 2022 · 2 comments
Closed

Support bucket_sort aggregation #123719

iuriikhrystiuk opened this issue Jan 25, 2022 · 2 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. loe:medium Medium Level of Effort

Comments

@iuriikhrystiuk
Copy link

Describe the feature:
There are multiple visualizations that allow to apply buket_script aggregations in one way or another. However, when we are talking about ordering terms in terms aggregations by the values, calculated in bucket_script, this is not allowed. There are use-cases when we need to show top terms ordered by the values calculated in the bucket_script.

Describe a specific use case for the feature:
Prerequisite: index, with documents, that contain following fields:

  • effectiveDate: a date field to apply date histogram on
  • tenantName: a keyword field that is used to break down visualization
  • receivedCount: a double field, used in percentage calculations
  • totalCount: a double field, used in percentage calculations

Use Case:
Plot percentage of receivedCount over effectiveDate daily broken down by tenantName. Order tenantName by percentage of receivedCount descending and display only top 5 tenantName values.

@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 25, 2022
@Dosant Dosant added enhancement New value added to drive a business result Feature:Aggregations Aggregation infrastructure (AggConfig, esaggs, ...) Team:AppServicesSv and removed needs-team Issues missing a team label labels Jan 31, 2022
@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:medium Medium Level of Effort labels Jan 31, 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
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, ...) impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:medium Medium Level of Effort
Projects
None yet
Development

No branches or pull requests

4 participants