# PUT mappings API overriding the exsisting mappings

**URL:** <https://discuss.elastic.co/t/put-mappings-api-overriding-the-exsisting-mappings/267055>\
**Category:** Elasticsearch\
**Created:** [March 12, 2021, 8:23am UTC](https://discuss.elastic.co/t/put-mappings-api-overriding-the-exsisting-mappings/267055 "2021-03-12T08:23:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nishikant\_Tayade](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nishikant_tayade/32/84159_2.png) [@Nishikant\_Tayade](https://discuss.elastic.co/u/Nishikant_Tayade)\
**Post date:** [March 12, 2021, 8:23am UTC](https://discuss.elastic.co/t/put-mappings-api-overriding-the-exsisting-mappings/267055/1 "2021-03-12T08:23:06Z")

</div>

Hello,

I have created an index template, where I am defining an "ignore\_above" mapping parameter for a "keyword" field type.

Now I want to update the mappings and want to add a new parameter "eager\_global\_ordinals" for the same "keyword" field using the PUT mappings API,

I can see the API returning 200OK.

So to verify the mapping when I call GET index-name, I can see the new mappings "eager\_global\_ordinals", but not able to see "ignore\_above"?

I checked, and found out that "ignore\_above" property is getting overrided with default value?

Meaning PUT mappings API overriding the mappings parameter to default value, if i dont pass any.

is there any way to avoid this behavior?

Any help is much appreciated!! Thank You!

---

<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:** [April 9, 2021, 8:23am UTC](https://discuss.elastic.co/t/put-mappings-api-overriding-the-exsisting-mappings/267055/2 "2021-04-09T08:23:21Z")

</div>

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