# How to reduce index mapping fields while keeping data continuity

**URL:** <https://discuss.elastic.co/t/how-to-reduce-index-mapping-fields-while-keeping-data-continuity/260376>\
**Category:** Elasticsearch\
**Created:** [January 6, 2021, 5:32pm UTC](https://discuss.elastic.co/t/how-to-reduce-index-mapping-fields-while-keeping-data-continuity/260376 "2021-01-06T17:32:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![NadavKal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nadavkal/32/70971_2.png) [@NadavKal](https://discuss.elastic.co/u/NadavKal)\
**Post date:** [January 6, 2021, 5:32pm UTC](https://discuss.elastic.co/t/how-to-reduce-index-mapping-fields-while-keeping-data-continuity/260376/1 "2021-01-06T17:32:50Z")

</div>

my issue is like this.  
I am trying to switch a dynamic mapping to static without impacting the users.  
We have many text and keyword fields which are redundant.  
the trick is... if field A has both A (text) and A.keyword (keyword)  
and the mapping looks like:

```auto
'A': {'type': 'text',
  'fields': {'keyword': {'type': 'keyword', 'ignore_above': 256}}},

```

how do I keep only the A.keyword field (delete the A field) without impacting the structure and naming of the fields?

---

<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:** [January 6, 2021, 8:28pm UTC](https://discuss.elastic.co/t/how-to-reduce-index-mapping-fields-while-keeping-data-continuity/260376/2 "2021-01-06T20:28:11Z")

</div>

How are you approaching the broader changes without any impact?

---

<div class="post-metadata">

**Author:** ![NadavKal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nadavkal/32/70971_2.png) [@NadavKal](https://discuss.elastic.co/u/NadavKal)\
**Post date:** [January 7, 2021, 5:21am UTC](https://discuss.elastic.co/t/how-to-reduce-index-mapping-fields-while-keeping-data-continuity/260376/3 "2021-01-07T05:21:12Z")

</div>

@warkolm  
I'm sorry. I don't follow.  
what do you mean by broader changes?

---

<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:** [January 11, 2021, 12:05am UTC](https://discuss.elastic.co/t/how-to-reduce-index-mapping-fields-while-keeping-data-continuity/260376/4 "2021-01-11T00:05:39Z")

</div>

You can't make these changes without a reindex. You can use aliases to reduce the impact to users, but there's no guarantee of _no_ impact.

---

<div class="post-metadata">

**Author:** ![NadavKal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nadavkal/32/70971_2.png) [@NadavKal](https://discuss.elastic.co/u/NadavKal)\
**Post date:** [January 20, 2021, 1:28pm UTC](https://discuss.elastic.co/t/how-to-reduce-index-mapping-fields-while-keeping-data-continuity/260376/5 "2021-01-20T13:28:17Z")

</div>

@warkolm ok. thanks

---

<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:** [February 17, 2021, 1:28pm UTC](https://discuss.elastic.co/t/how-to-reduce-index-mapping-fields-while-keeping-data-continuity/260376/6 "2021-02-17T13:28:29Z")

</div>

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