# Field mapping conflict on shrink index **URL:** \ **Category:** Elasticsearch\ **Created:** [March 25, 2020, 6:20pm UTC](https://discuss.elastic.co/t/field-mapping-conflict-on-shrink-index/225039 "2020-03-25T18:20:58Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![alexolivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexolivan/32/57425_2.png) [@alexolivan](https://discuss.elastic.co/u/alexolivan)\ **Post date:** [March 25, 2020, 6:20pm UTC](https://discuss.elastic.co/t/field-mapping-conflict-on-shrink-index/225039/1 "2020-03-25T18:20:58Z")
Hi forum. I'm experiencing a problem that has caught me by surprise... all of the sudden, kibana starts complaining I've got a conflicting field on my indexes. The field is a classic bytes field, wich is suposed (and as far as I know is) integer (well, I set to INT on logstash grok patterns... and has worked to me since the early ELK 1.5) Kibana complains my index logstash-webservers-000002 has long type 'bytes' field ... but shrink-webservers-000001 is text .... Since I'm 'mixing' o my index bytes fileds from several logfiles (NGINX, Apache2, ICecast2...) , It could be that I'm getting leaked text byte fields ... but I's has been working fine till now. On the other hand, I'm experimenting with ILM (I go t a default logstash-\* index template, and a logstash-webservers-\* template where I set the ILM policy) ... and , well it works!!! but ... what's happenning here? ... Should I create a shrink-logstash-webservers-\* template too? Best regards ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 22, 2020, 6:21pm UTC](https://discuss.elastic.co/t/field-mapping-conflict-on-shrink-index/225039/2 "2020-04-22T18:21:08Z")
Closed on April 22, 2020, 6:21pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.