# Elasticsearch mapping issue for ES version 7.\* **URL:** \ **Category:** Logstash\ **Created:** [November 3, 2022, 2:28pm UTC](https://discuss.elastic.co/t/elasticsearch-mapping-issue-for-es-version-7/318114 "2022-11-03T14:28:40Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![sssamant](https://avatars.discourse-cdn.com/v4/letter/s/eada6e/32.png) [@sssamant](https://discuss.elastic.co/u/sssamant)\ **Post date:** [November 3, 2022, 2:28pm UTC](https://discuss.elastic.co/t/elasticsearch-mapping-issue-for-es-version-7/318114/1 "2022-11-03T14:28:40Z")
Hello, We are facing some issue related to mapping when we ingest data. Here is error we are getting: "error"=\>{"type"=\>"illegal\_argument\_exception", "reason"=\>"Mapper for [fn.keyword] conflicts with existing mapper:\n\tCannot update parameter [normalizer] from [custom\_normalizer] to [default]"}}} ---
**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:** [November 4, 2022, 1:29am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-issue-for-es-version-7/318114/2 "2022-11-04T01:29:07Z")
As the error suggests, you cannot change mapping for a field that already exists. You need to look at the `_mapping` endpoint for the existing index to see what it's already set as. Then if you want to change it you will need to create a new index with the mapping you want and then reindex the older data into it. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 2, 2022, 1:29am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-issue-for-es-version-7/318114/3 "2022-12-02T01:29:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.