-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Sort and truncate pipeline aggregation #14928
Labels
Comments
This was referenced Nov 23, 2015
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1 It is quite surprising that |
+1 |
1 similar comment
+1 |
Any ideas when this will be in production? |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
1 similar comment
+1 |
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this issue
Nov 7, 2017
This commit adds a parent pipeline aggregation that allows sorting the buckets of a parent multi-bucket aggregation. The aggregation also offers [from] and [size] parameters in order to truncate the result as desired. Closes elastic#14928
dimitris-athanasiou
added a commit
that referenced
this issue
Nov 9, 2017
This commit adds a parent pipeline aggregation that allows sorting the buckets of a parent multi-bucket aggregation. The aggregation also offers [from] and [size] parameters in order to truncate the result as desired. Closes #14928
dimitris-athanasiou
added a commit
that referenced
this issue
Nov 10, 2017
This commit adds a parent pipeline aggregation that allows sorting the buckets of a parent multi-bucket aggregation. The aggregation also offers [from] and [size] parameters in order to truncate the result as desired. Closes #14928
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This would be a parent pipeline aggregation which would take the following option:
offset + size
index in the sorted buckets list will be removed. Defaults tobuckets.size()
(i.e. don't remove any buckets from the end of the list)The text was updated successfully, but these errors were encountered: