# How to disable index migration on mapping change

**URL:** <https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561>\
**Category:** Kibana\
**Created:** [May 10, 2019, 1:02pm UTC](https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561 "2019-05-10T13:02:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ENG618](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eng618/32/59206_2.png) [@ENG618](https://discuss.elastic.co/u/ENG618)\
**Post date:** [May 10, 2019, 1:02pm UTC](https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561/1 "2019-05-10T13:02:31Z")

</div>

While upgrading my plugin (from: 5.6, to: 6.5), I have updated some mappings. This seems to be causing kibana to think it needs to migrate data, and causing the below error.

```auto
server log [21:06:03.159] [error][status][plugin:spaces@6.5.4] Status changed from yellow to red - mapping set to strict, dynamic introduction of [default] within [search] is not allowed
server error [21:06:03.163] [fatal][root] Error: mapping set to strict, dynamic introduction of [default] within [search] is not allowed
    at Object.write (/Users/<user-path>/kibana/src/server/saved_objects/migrations/core/elastic_index.ts:106:23)
    at <anonymous>

 FATAL Error: mapping set to strict, dynamic introduction of [default] within [search] is not allowed

 server crashed with status code 1

```

Is there an easy way to disable this migration check.

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [May 14, 2019, 4:21pm UTC](https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561/2 "2019-05-14T16:21:20Z")

</div>

Have you migrated your 5.6 index to remove types by either using the Upgrade Assistant or [manually](https://www.elastic.co/guide/en/kibana/6.5/migrating-6.0-index.html)?

Additionally, [here](https://github.com/elastic/kibana/blob/master/src/legacy/server/saved_objects/migrations/README.md) is more information regarding how the automatic migrations work which were added in 6.5.

---

<div class="post-metadata">

**Author:** ![ENG618](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eng618/32/59206_2.png) [@ENG618](https://discuss.elastic.co/u/ENG618)\
**Post date:** [May 16, 2019, 8:09pm UTC](https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561/3 "2019-05-16T20:09:30Z")

</div>

> [@tylersmalley](#):
>
> Have you migrated your 5.6 index to remove types by either using the Upgrade Assistant or [manually](https://www.elastic.co/guide/en/kibana/6.5/migrating-6.0-index.html)?

Updated manually.

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [May 16, 2019, 10:18pm UTC](https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561/4 "2019-05-16T22:18:33Z")

</div>

Was this done prior to upgrading to 6.x? What does `GET .kibana/_mapping` look like?

---

<div class="post-metadata">

**Author:** ![ENG618](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eng618/32/59206_2.png) [@ENG618](https://discuss.elastic.co/u/ENG618)\
**Post date:** [May 23, 2019, 8:34pm UTC](https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561/5 "2019-05-23T20:34:37Z")

</div>

yes, it was done prior to the upgrade

---

<div class="post-metadata">

**Author:** ![ENG618](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eng618/32/59206_2.png) [@ENG618](https://discuss.elastic.co/u/ENG618)\
**Post date:** [June 4, 2019, 5:12pm UTC](https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561/6 "2019-06-04T17:12:21Z")

</div>

We have custom fields mapped on `dashboards`, `visualizations`, `searches`. There were also a few we let get dynamically mapped.

Now that `dynamic` is set to strict it fails.

---

<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 2, 2019, 5:25pm UTC](https://discuss.elastic.co/t/how-to-disable-index-migration-on-mapping-change/180561/7 "2019-07-02T17:25:15Z")

</div>

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