# Pipelined Histogram Aggregation?

**URL:** https://discuss.elastic.co/t/pipelined-histogram-aggregation/63783
**Category:** Elasticsearch
**Created:** [October 24, 2016, 5:39pm UTC](https://discuss.elastic.co/t/pipelined-histogram-aggregation/63783 "2016-10-24T17:39:22Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Buck\_Evan](https://avatars.discourse-cdn.com/v4/letter/b/919ad9/32.png) [@Buck\_Evan](https://discuss.elastic.co/u/Buck_Evan)
#### Post date: [October 27, 2016, 8:11pm UTC](https://discuss.elastic.co/t/pipelined-histogram-aggregation/63783/6 "2016-10-27T20:11:05Z")

</div>

Thanks Christian. That's what we're working on implementing right now, as a workaround for not being able to express the above query.

The drawback, that I'd like to eliminate, is that we need to keep one index per "first order" aggregation that we want to support. This means we only support use cases that we've thought of way before the user wants them.

If I can do this without pre-aggregation, it means that I instead support arbitrary use cases.

Related discussions:

- [Reasonable feature request? map-reduce sibling pipeline aggregations](https://discuss.elastic.co/t/reasonable-feature-request-map-reduce-sibling-pipeline-aggregations/64194)
- [https://github.com/elastic/elasticsearch/issues/21097](https://github.com/elastic/elasticsearch/issues/21097)

---

_[View the full topic](https://discuss.elastic.co/t/pipelined-histogram-aggregation/63783)._