# Managing aggregations (facets)

**URL:** <https://discuss.elastic.co/t/managing-aggregations-facets/80272>\
**Category:** Elasticsearch\
**Created:** [March 28, 2017, 10:03am UTC](https://discuss.elastic.co/t/managing-aggregations-facets/80272 "2017-03-28T10:03:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bart\_Kooijman](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@Bart\_Kooijman](https://discuss.elastic.co/u/Bart_Kooijman)\
**Post date:** [March 28, 2017, 10:03am UTC](https://discuss.elastic.co/t/managing-aggregations-facets/80272/1 "2017-03-28T10:03:59Z")

</div>

Hi All,

The company I work for has well over 200 facets configured in its current (eCommerce) search engine. Our business manages them including activation, deletion, archiving and things like spans and coverage. Managing such a huge amount of aggregations in Elasticsearch is a quite labor intensive challenge. Does anyone know of a solution to make it more easy to manage such huge amount of facets? If yes, how does it work?

Thanks in advance,

Bart.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 25, 2017, 10:04am UTC](https://discuss.elastic.co/t/managing-aggregations-facets/80272/2 "2017-04-25T10:04:25Z")

</div>

Closed on April 25, 2017, 10:04am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.