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 min_doc_count support to range aggregations #10027

Closed
halilim opened this issue Mar 7, 2015 · 4 comments
Closed

Add min_doc_count support to range aggregations #10027

halilim opened this issue Mar 7, 2015 · 4 comments

Comments

@halilim
Copy link

halilim commented Mar 7, 2015

Currently, range aggregations doesn't have min_doc_count support AFAIK. As a temporary solution client-side filtering could be used but being able to filter out empty buckets from range aggregations (and from other aggregations if possible) would be neater.

@jpountz
Copy link
Contributor

jpountz commented Mar 16, 2015

This is something we started discussing on #8110. The issue has been closed since it probably had too much scope, but essentially we are thinking/working on adding the ability to do more stuff at reduce time (when all shard responses get merged) and filtering of the reduced buckets could certainly be done this way. Hopefully this would also allow to have a single way to filter buckets instead of having to implement it for every aggregation.

@clintongormley
Copy link

@colings86 any thoughts about this?

@colings86
Copy link
Contributor

With the addition of the bucket selector pipeline aggregation in 2.0 you can now filter buckets of any aggregation type at reduce time for minimum doc count or any other criteria

@clintongormley
Copy link

thanks @colings86 - closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants