# Field mapping: "ignore\_above" and "index" settings

**URL:** <https://discuss.elastic.co/t/field-mapping-ignore-above-and-index-settings/316235>\
**Category:** Elasticsearch\
**Created:** [October 10, 2022, 2:24pm UTC](https://discuss.elastic.co/t/field-mapping-ignore-above-and-index-settings/316235 "2022-10-10T14:24:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gdd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gdd/32/99260_2.png) [@gdd](https://discuss.elastic.co/u/gdd)\
**Post date:** [October 10, 2022, 2:24pm UTC](https://discuss.elastic.co/t/field-mapping-ignore-above-and-index-settings/316235/1 "2022-10-10T14:24:36Z")

</div>

I experienced bulks by logstash returning some errors,

The template contained this mapping for event.original field:  
{"index": false, "type": "keyword", "doc\_values": false }

The unexpected solution has been the introduction of "ignore\_above" as below:  
{"ignore\_above": 1024,"index": false, "type": "keyword", "doc\_values": false }

This seems very strange to me because I expected that the clause \<"index": false\> was enough to avoid indexing the values of this field (as explaned under [index | Elasticsearch Guide [8.4] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-index.html)).

Am I wrong supposing that "index": false should be enough?

---

<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:** [November 7, 2022, 2:24pm UTC](https://discuss.elastic.co/t/field-mapping-ignore-above-and-index-settings/316235/2 "2022-11-07T14:24:48Z")

</div>

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