Trying to parse an object but has a different type – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Trying to parse an object but has a different type ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Trying to parse an object but has a different type [“classname  is ObjectMapper.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (type.equals(CONTENT_TYPE)) {
 builder.nested = Nested.NO;
 } else if (type.equals(NESTED_CONTENT_TYPE)) {
 nested = true;
 } else {
 throw new MapperParsingException("Trying to parse an object but has a different type [" + type
 + "] for [" + name + "]");
 }
 }
 fieldNode = node.get("include_in_parent");
 if (fieldNode != null) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content