# ELK 5.4 - LS reverts to automatic mapping when 'type' field is removed or renamed **URL:** \ **Category:** Logstash\ **Created:** [June 8, 2017, 11:17am UTC](https://discuss.elastic.co/t/elk-5-4-ls-reverts-to-automatic-mapping-when-type-field-is-removed-or-renamed/88704 "2017-06-08T11:17:15Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 10, 2017, 6:34am UTC](https://discuss.elastic.co/t/elk-5-4-ls-reverts-to-automatic-mapping-when-type-field-is-removed-or-renamed/88704/2 "2017-06-10T06:34:35Z")
I'll close this one as there's a bit of history in the other one, please just edit the subject as mentioned 🙂 > [@ELK 5.4 - LS reverts to automatic mapping when 'type' field is removed or renamed - ultimate slight\_smile](https://discuss.elastic.co/t/elk-stack-5-4-removing-field-named-type-creates-new-mapping-named-logs/88534): > > Hi, I'm having an issue with removing the field named "type". I have created an index template for my data and declare a type "MyType". Ingesting data with logstash works very well, but I get an extra field named "type" with the value "MyType" which I did not want (I do not mean the field "\_type", which I can make disappear by changing Kibana settings). Is this field generated by Logstash or by Elasticsearch? When I remove that field in my logstash conf, it actually disappears, but a myster… --- _[View the full topic](https://discuss.elastic.co/t/elk-5-4-ls-reverts-to-automatic-mapping-when-type-field-is-removed-or-renamed/88704)._