Error parsing field ” + name() + “; expected an object but got – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” error parsing field ” + name() + “; expected an object but got ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “error parsing field [” + name() + “]; expected an object but got”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 range = new Range(rangeType; from; to; includeFrom; includeTo);
 } else if (fieldType().rangeType == RangeType.IP && start == XContentParser.Token.VALUE_STRING) {
 range = parseIpRangeFromCidr(parser);
 } else {
 throw new MapperParsingException("error parsing field [" + name() + "]; expected an object but got " + parser.currentName());
 context.doc().addAll(fieldType().rangeType.createFields(context; name(); range; index; hasDocValues; store)); 
 if (hasDocValues == false && (index || store)) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content