# Significant terms aggregation on analyzed text field

**URL:** <https://discuss.elastic.co/t/significant-terms-aggregation-on-analyzed-text-field/63331>\
**Category:** Kibana\
**Created:** [October 18, 2016, 9:54pm UTC](https://discuss.elastic.co/t/significant-terms-aggregation-on-analyzed-text-field/63331 "2016-10-18T21:54:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patrick\_Lam](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@Patrick\_Lam](https://discuss.elastic.co/u/Patrick_Lam)\
**Post date:** [October 18, 2016, 9:54pm UTC](https://discuss.elastic.co/t/significant-terms-aggregation-on-analyzed-text-field/63331/1 "2016-10-18T21:54:53Z")

</div>

Hi,

I'm trying to build a simple visualization that lists the top N significant terms in a data table and then include it in a dashboard. I'm doing this on an analyzed text field for a relatively large index that frankly stretches our hardware to the max. The issue is that the aggregation and visualization on the dashboard works perfectly fine for any number of queries and filters that shrinks the dataset significantly. However, the default "start" for the dashboard is the entire large index and sometimes users will actually want to see our dashboard visualizations for the entire index before filtering down.

So the problem is that running significant terms on the entire index takes too long and times out. I can set the timeout rate higher, but frankly I just don't want the dashboard to take forever to load. However, because the significant terms is only one part of the dashboard, having that one visualization time out automatically times out every other visualization on the dashboard even though the other ones run quickly.

I can think of a couple theoretical solutions that I'm not sure exist:

1. Is there a way to make the dashboard visualizations load separately? That is, is there a way to set it such that the other visualizations on the same dashboard still load even if one of the visualizations times out? Or alternatively, is there a way to "switch off" one of the visualizations on a dashboard when the index is too large without filters?

2. Is there an implementation of the sampler aggregation in Kibana? I'm guessing this would significantly reduce the load on the aggregation.

Are there any other potential non-hardware solutions to this problem?

---

<div class="post-metadata">

**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\
**Post date:** [October 18, 2016, 11:20pm UTC](https://discuss.elastic.co/t/significant-terms-aggregation-on-analyzed-text-field/63331/2 "2016-10-18T23:20:39Z")

</div>

Hey Patrick

1. Kibana dashboards always load as one request, and that's not likely to change unless browsers start supporting concurrent requests to a single hostname. It was a primary issue that we aimed to solve when starting Kibana 4.

2. I have never heard of the sampler aggregation, it looks pretty cool! There isn't any way to use it in Kibana today, though it could be a great feature! I suggest filing an issue in the repo.

---

<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:** [July 6, 2017, 1:36pm UTC](https://discuss.elastic.co/t/significant-terms-aggregation-on-analyzed-text-field/63331/3 "2017-07-06T13:36:19Z")

</div>