# Hierarchy, Facets and Facet Plugins **URL:** \ **Category:** Elasticsearch\ **Created:** [December 10, 2012, 6:12pm UTC](https://discuss.elastic.co/t/hierarchy-facets-and-facet-plugins/10020 "2012-12-10T18:12:27Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Will\_Pugh](https://avatars.discourse-cdn.com/v4/letter/w/e99b99/32.png) [@Will\_Pugh](https://discuss.elastic.co/u/Will_Pugh)\ **Post date:** [December 10, 2012, 6:12pm UTC](https://discuss.elastic.co/t/hierarchy-facets-and-facet-plugins/10020/1 "2012-12-10T18:12:27Z")
Hey folks, ElasticSearch looks really promising to me, and hits about 90% of my use cases pretty directly. In terms of analyzing features, the main gaps I see are around hierarchical facets ([https://github.com/elasticsearch/elasticsearch/issues/1076](https://github.com/elasticsearch/elasticsearch/issues/1076)). I really only need this around terms and statistical facets. I saw some other threads around building facet plugins, looking at the API it seems like it would be possible to write a custom plugin for this. It would he hard to be as performant as the faceting in the core product (mainly due to additional garbage that would need to be created around building the hierarchy), but my guess is that I could hit my own performance requirements. Does this seem like a reasonable approach? Am I missing something? Has anyone done this already? ``` Thanks, --Will ``` -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:00am UTC](https://discuss.elastic.co/t/hierarchy-facets-and-facet-plugins/10020/2 "2017-07-06T03:00:31Z")