Trying to parse an object but has a different type – Elasticsearch Error How To Solve Related Issues



Trying to parse an object but has a different type – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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) {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 How to solve MapperParsingException: object mapping for [test] tried to parse as object, but got EOF -views 45,152 ,score 26

Elastic search parse as object but found nested values -views   35,score 1



Find Configuration Errors

Analyze Now