Field mapper name is defined more than once – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.1-8.9

Briefly, this error occurs when a field in Elasticsearch is defined multiple times in the same index. This could be due to a mapping conflict or a mistake in the index creation process. To resolve this issue, you can either delete and recreate the index with the correct mapping or update the mapping of the existing index to remove the duplicate field. Also, ensure that the data being indexed doesn’t contain duplicate fields.

This guide will help you check for common problems that cause the log ” Field [” + + “] is defined more than once ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “Field [” + + “] is defined more than once” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 for (FieldMapper mapper : mappers) {
 if (objects.containsKey( {
 throw new MapperParsingException("Field [" + + "] is defined both as an object and a field");
 if (fieldMappers.put(; mapper) != null) {
 throw new MapperParsingException("Field [" + + "] is defined more than once");
 if (mapper.hasScript()) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?