# Old Mapping in Index ReAppeared

**URL:** <https://discuss.elastic.co/t/old-mapping-in-index-reappeared/38008>\
**Category:** Elasticsearch\
**Created:** [December 27, 2015, 2:15pm UTC](https://discuss.elastic.co/t/old-mapping-in-index-reappeared/38008 "2015-12-27T14:15:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![code\_blue](https://avatars.discourse-cdn.com/v4/letter/c/7ea924/32.png) [@code\_blue](https://discuss.elastic.co/u/code_blue)\
**Post date:** [December 27, 2015, 2:15pm UTC](https://discuss.elastic.co/t/old-mapping-in-index-reappeared/38008/1 "2015-12-27T14:15:05Z")

</div>

We observed a strange issue in Elastic Search Cluster. We deleted a mapping and created a new mapping and then loaded all the data using one shot river.  
Search was working as expected, however the old mapping in the index reappeared out of no where.

Has any one faced a similar issue and how can we ensure the old mapping is not cached in Elastic Search.

---

<div class="post-metadata">

**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:** [December 27, 2015, 8:01pm UTC](https://discuss.elastic.co/t/old-mapping-in-index-reappeared/38008/2 "2015-12-27T20:01:37Z")

</div>

Check that it isn't a template as well?

> [@code\_blue](#):
>
> using one shot river

This would suggest you are using an old version of ES, so upgrading would be recommended too.

---

<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:** [July 5, 2017, 11:28pm UTC](https://discuss.elastic.co/t/old-mapping-in-index-reappeared/38008/3 "2017-07-05T23:28:25Z")

</div>