# Type conflict **URL:** \ **Category:** Kibana\ **Created:** [May 8, 2019, 3:12am UTC](https://discuss.elastic.co/t/type-conflict/180088 "2019-05-08T03:12:01Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![shwesinhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shwesinhan/32/78663_2.png) [@shwesinhan](https://discuss.elastic.co/u/shwesinhan)\ **Post date:** [May 8, 2019, 3:12am UTC](https://discuss.elastic.co/t/type-conflict/180088/1 "2019-05-08T03:12:01Z")
Hi there I got type conflict in kibana when new month started. here is my scenario. I use elapsed filter to get elapsed\_time in logstash. But later I added one grok pattern like `%{DATA:elapsed_time}` using same field name and I forgot the type aware. End of the month, I got type conflict in kibana. One thing I am wondering I use same structure demo/prod but it is ok in my demo env only happen in prod env. 🙄 ![Capture](https://us1.discourse-cdn.com/elastic/original/3X/2/5/250a444d94e69fe44456bf9eef5dabc5d630d1d2.png) Please kindly give suggestion how to solve this problem? 🤒 ---
**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\ **Post date:** [May 9, 2019, 3:38pm UTC](https://discuss.elastic.co/t/type-conflict/180088/2 "2019-05-09T15:38:11Z")
Float fields have doc\_values and will work with aggregations. Text fields do not have doc\_values on by default and will not work with aggregations. You will get shard failures for aggregation requests that use `elapsed_time` field and span the `logstash-2019.05` index. These shard failures will not harm your cluster, but they will prevent data from `logstash-2019.05` from being displayed in Kibana so you will have missing data in any visualization that uses the `elapsed_time` field and spans the `logstash-2019.05` index. If you never use elapsed\_time in any aggregations then there will never be a problem. If you use elapsed\_time in aggregations then you should re-index your `logstash-2019.05` so that elapsed\_time is mapped as a float. ---
**Author:** ![shwesinhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shwesinhan/32/78663_2.png) [@shwesinhan](https://discuss.elastic.co/u/shwesinhan)\ **Post date:** [May 10, 2019, 9:32am UTC](https://discuss.elastic.co/t/type-conflict/180088/3 "2019-05-10T09:32:11Z")
Thank you @Nathan_Reese Yes I use `elapsed_time` in several plots. I agree with you about missing data. Because when I check the plots, I faced data are gone but I saw them on discover. Oh something is wrong!! Then I found that `elapsed_time` type got conflict since end of Apr. 🤒 By re-index `logstash-2019.05`, elapsed\_time is mapped automatically as a float in new index? do i need to map manually? > If you use elapsed\_time in aggregations then you should re-index your `logstash-2019.05` so that elapsed\_time is mapped as a float. Thank you. ---
**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\ **Post date:** [May 10, 2019, 1:42pm UTC](https://discuss.elastic.co/t/type-conflict/180088/4 "2019-05-10T13:42:45Z")
[https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 7, 2019, 1:42pm UTC](https://discuss.elastic.co/t/type-conflict/180088/5 "2019-06-07T13:42:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.