# Kibana analyzed field warning

**URL:** <https://discuss.elastic.co/t/kibana-analyzed-field-warning/94867>\
**Category:** Kibana\
**Created:** [July 27, 2017, 9:12pm UTC](https://discuss.elastic.co/t/kibana-analyzed-field-warning/94867 "2017-07-27T21:12:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![santhosh](https://avatars.discourse-cdn.com/v4/letter/s/f07891/32.png) [@santhosh](https://discuss.elastic.co/u/santhosh)\
**Post date:** [July 27, 2017, 9:12pm UTC](https://discuss.elastic.co/t/kibana-analyzed-field-warning/94867/1 "2017-07-27T21:12:33Z")

</div>

Aggregation on analyzed fields used to give a warning message in earlier version of Kibana (\< v5) and if we proceed with it, an exception will be thrown, but with v5.4.1, it allows to aggregate on analyzed fields without a warning message and displays no result (No exception is thrown either).

Is this a bug or any additional features enabled here and I am not using it right?

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [July 28, 2017, 3:12pm UTC](https://discuss.elastic.co/t/kibana-analyzed-field-warning/94867/2 "2017-07-28T15:12:42Z")

</div>

hi @santhosh

maybe I misunderstand, but what kind of aggregation are you trying to run an an analyzed fields ?

Kibana will filter out the analyzed fields when trying to do a terms-aggregation on them. E.g. you can see which fields are analyzed in the index-pattern summary

For example, from the image below, I will not be able to do a terms-aggregation on `relatedConent.og:type`

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/8/98d0cf496caad80d0d2dd9b8cd4ca3a9c213937b.png)

---

<div class="post-metadata">

**Author:** ![santhosh](https://avatars.discourse-cdn.com/v4/letter/s/f07891/32.png) [@santhosh](https://discuss.elastic.co/u/santhosh)\
**Post date:** [July 28, 2017, 6:38pm UTC](https://discuss.elastic.co/t/kibana-analyzed-field-warning/94867/3 "2017-07-28T18:38:44Z")

</div>

Hi @thomasneirynck

I work in ELK for more than a year and I'm aware that aggregations can't be done on analyzed field. Recently, I was trying to aggregate a field thinking it's non-analyzed with an assumption from previous experience that I'll be warned if I do a mistake. I didn't get warned, but got an empty result, which is misleading (It made me think the query I used doesn't have any data). Later I found that was analyzed field.

What I am saying is, the warning/exception when an user trying to aggregate on analyzed field is missing which was available earlier. The question is, is this a bug?

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [July 28, 2017, 6:47pm UTC](https://discuss.elastic.co/t/kibana-analyzed-field-warning/94867/4 "2017-07-28T18:47:53Z")

</div>

Where in Kibana did you run that query? In Console? Or did this happen in Visualize when designing a visualization?

---

<div class="post-metadata">

**Author:** ![santhosh](https://avatars.discourse-cdn.com/v4/letter/s/f07891/32.png) [@santhosh](https://discuss.elastic.co/u/santhosh)\
**Post date:** [July 28, 2017, 7:12pm UTC](https://discuss.elastic.co/t/kibana-analyzed-field-warning/94867/5 "2017-07-28T19:12:20Z")

</div>

Ok, the problem is resolved. My bad, I was doing it without refreshing my indices after kibana upgrade. Once I refreshed, it's resolved. And I liked the way it is handled now.

PS: I run in visualize while designing a visualization.

Thanks,

---

<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:** [August 25, 2017, 7:12pm UTC](https://discuss.elastic.co/t/kibana-analyzed-field-warning/94867/6 "2017-08-25T19:12:40Z")

</div>

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