# Unexpected mapping?

**URL:** <https://discuss.elastic.co/t/unexpected-mapping/96739>\
**Category:** Logstash\
**Created:** [August 11, 2017, 9:25am UTC](https://discuss.elastic.co/t/unexpected-mapping/96739 "2017-08-11T09:25:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TimWard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timward/32/19574_2.png) [@TimWard](https://discuss.elastic.co/u/TimWard)\
**Post date:** [August 11, 2017, 9:25am UTC](https://discuss.elastic.co/t/unexpected-mapping/96739/1 "2017-08-11T09:25:39Z")

</div>

I discovered that there's a mapping in Elasticsearch for a field that I wasn't expecting to be there, as that field is not present in any documents that are indexed (and was not present in any template).

The field _is_ (sometimes) created during Logstash processing, but when it's created it is always removed again by a "remove\_field" and so never gets as far as Elasticsearch.

So why does Elasticsearch have a mapping for this field it has never seen?

---

<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:** [September 8, 2017, 9:25am UTC](https://discuss.elastic.co/t/unexpected-mapping/96739/2 "2017-09-08T09:25:48Z")

</div>

Closed on September 8, 2017, 9:25am UTC

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