# Newly added Field Not available for aggregations **URL:** \ **Category:** Kibana\ **Created:** [January 13, 2021, 8:31pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050 "2021-01-13T20:31:39Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![lzukel](https://avatars.discourse-cdn.com/v4/letter/l/4491bb/32.png) [@lzukel](https://discuss.elastic.co/u/lzukel)\ **Post date:** [January 13, 2021, 8:31pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/1 "2021-01-13T20:31:39Z")
Elasticsearch 7.9.1 Kibana 7.9.1 - 4 docker containers Updated the index mapping to add new field of type keyword. Waited for new index to be created. Refreshed the index pattern in Kibana. Searched for that field in the Field list in kibana. - field is string, searchable and aggregatable Field shows up as unknown field in discover When trying to create a visualization and aggregate by this field, I cannot find the new field in terms list. Side note: when refreshing the index pattern, the field would show up then disappear a few moments later, at which point I would have to refresh the index pattern again. ---
**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:** [January 13, 2021, 11:08pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/2 "2021-01-13T23:08:04Z")
hi @lzukel, - What is the actual mapping of that field in Elasticsearch? - Do you have documents that have populated values for that field (or does it only exist in the Elasticsearch-mapping)? ---
**Author:** ![lzukel](https://avatars.discourse-cdn.com/v4/letter/l/4491bb/32.png) [@lzukel](https://discuss.elastic.co/u/lzukel)\ **Post date:** [January 15, 2021, 4:13pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/3 "2021-01-15T16:13:35Z")
the mapping for the field is keyword. Yes there are many documents that have populated with that field ---
**Author:** ![lzukel](https://avatars.discourse-cdn.com/v4/letter/l/4491bb/32.png) [@lzukel](https://discuss.elastic.co/u/lzukel)\ **Post date:** [January 15, 2021, 4:35pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/4 "2021-01-15T16:35:25Z")
![Screen Shot 2021-01-15 at 9.25.01 AM](https://us1.discourse-cdn.com/elastic/original/3X/a/1/a15966287840146de8ffbf3630d3380eba270b63.png) ![Screen Shot 2021-01-15 at 9.26.34 AM](https://us1.discourse-cdn.com/elastic/original/3X/d/e/defdffe3344fa6465fa55f99cf8009c9c79d815a.png) ![Screen Shot 2021-01-15 at 9.27.22 AM](https://us1.discourse-cdn.com/elastic/original/3X/b/b/bb3c5ae7edb709cc6d07c7f10da73e2789945768.png) After refreshing the index template page... The field has mysteriously disappeared from the index pattern: ![Screen Shot 2021-01-15 at 9.28.02 AM](https://us1.discourse-cdn.com/elastic/original/3X/1/4/1495767e62cf50295fcc9f044fd8007f74b06aa6.png) When searching that field in the discover tab with that index pattern there is no cached mapping for that field: ![Screen Shot 2021-01-15 at 9.33.55 AM](https://us1.discourse-cdn.com/elastic/original/3X/d/e/dea3013f09cd2cb65ea8a0e99083cc1da4345758.png) ---
**Author:** ![lzukel](https://avatars.discourse-cdn.com/v4/letter/l/4491bb/32.png) [@lzukel](https://discuss.elastic.co/u/lzukel)\ **Post date:** [January 20, 2021, 4:16pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/5 "2021-01-20T16:16:39Z")
Any ideas? This is a blocking issue for some users ---
**Author:** ![lzukel](https://avatars.discourse-cdn.com/v4/letter/l/4491bb/32.png) [@lzukel](https://discuss.elastic.co/u/lzukel)\ **Post date:** [January 26, 2021, 4:08pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/6 "2021-01-26T16:08:01Z")
@thomasneirynck still need help resolving this issue ---
**Author:** ![lzukel](https://avatars.discourse-cdn.com/v4/letter/l/4491bb/32.png) [@lzukel](https://discuss.elastic.co/u/lzukel)\ **Post date:** [February 8, 2021, 7:03pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/7 "2021-02-08T19:03:10Z")
Bump... This is still an issue ---
**Author:** ![lzukel](https://avatars.discourse-cdn.com/v4/letter/l/4491bb/32.png) [@lzukel](https://discuss.elastic.co/u/lzukel)\ **Post date:** [February 11, 2021, 5:21pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/8 "2021-02-11T17:21:29Z")
Upon further inspection, I am seeing the following error in Kibana logs when trying to refresh the index\_pattern: ``` {"type":"error","@timestamp":"2021-02-11T17:15:51Z","tags":[],"pid":16,"level":"error","error":{"message":"Internal Server Error","name":"Error","stack":"Error: Internal Server Error\n at HapiResponseAdapter.toError (/usr/share/kibana/src/core/server/http/router/response_adapter.js:132:19)\n at HapiResponseAdapter.toHapiResponse (/usr/share/kibana/src/core/server/http/router/response_adapter.js:86:19)\n at HapiResponseAdapter.handle (/usr/share/kibana/src/core/server/http/router/response_adapter.js:81:17)\n at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:162:34)\n at process._tickCallback (internal/process/next_tick.js:68:7)"},"url":{"protocol":null,"slashes":null,"auth":null,"host":null,"port":null,"hostname":null,"hash":null,"search":null,"query":{},"pathname":"/api/saved_objects/index-pattern/8be439c0-cd83-11e8-8da8-33f92a7b1a47","path":"/api/saved_objects/index-pattern/8be439c0-cd83-11e8-8da8-33f92a7b1a47","href":"/api/saved_objects/index-pattern/8be439c0-cd83-11e8-8da8-33f92a7b1a47"},"message":"Internal Server Error"} ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 11, 2021, 5:22pm UTC](https://discuss.elastic.co/t/newly-added-field-not-available-for-aggregations/261050/9 "2021-03-11T17:22:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.